🌱 Seamless Cross-Chain for the Neo Ecosystem 🌱
“Oh, my token is on Neo X… wait, no, it’s on Neo N3… omg, omg, what should I do?” In the end, it shouldn’t matter! Our goal is to make assets on Neo N3 and Neo X feel like they’re on the same chain! 🚀 💚
The Neo X Native Bridge enables seamless token interoperability between Neo N3 and Neo X. To maintain security, reliability, and long-term sustainability, we have established clear requirements for token listings.
If you believe your token is a good fit, please review the requirements below and submit a request for evaluation.
Tokens should meet specific criteria to be listed on the Neo X Native Bridge.
To ensure ecosystem sustainability and long-term adoption, tokens must meet the following criteria:
✅ Token Traction – The token must demonstrate adequate traction on its native chain.
✅ Ecosystem Stickiness – The token should have a proven history or a long-term roadmap commitment to the Neo ecosystem.
✅ Roadmap & Integrity – A publicly available roadmap and a track record of consistent development and delivery.
✅ Team Information – A clear disclosure of core team members.
To guarantee security and smooth functionality across chains, the following technical conditions must be met:
🔒 Smart Contract Security
❌ No Upgradable Smart Contracts – Token contracts must be immutable once deployed.
✅ Audit Reports – The token smart contract must be audited on both Neo N3 and Neo X, with reports publicly available.
✅ Open-Source Code – The source code for both versions (Neo N3 & Neo X) must be public, with proof that the deployed contract matches the published source code.
⚙️ Token Standards & Deployment
✅ NEP-17 Standard – The token must be NEP-17 compliant on Neo N3.
✅ ERC-20 Standard – The token must be ERC-20 compliant on Neo X.
✅ Deployment Freshness – Token smart contracts must be newly deployed on the destination chain.
📌 Contract-Specific Rules
🏷️ Contract Addresses – The token contract address must be provided for both Neo N3 and Neo X.
🔄 Transfer Method Compliance – On Neo N3, the Transfer() method MUST always return true/false and MUST NEVER abort or throw exceptions when sending to an externally owned account (EOA).
🔢 Decimal Precision – The difference in decimals between the Neo N3 and Neo X versions CANNOT exceed 36.
🛠️ Bane Labs Templates – Projects must use the official Bane Labs templates for NEP-17/ERC-20 deployment on the destination chain.
⚖ Token Type Support
✅ Fixed Supply – Fully supported.
⚠️ Uncapped Supply – Requires case-by-case analysis (takes longer).
If your token meets the criteria above, you can submit a listing request through the form below. The Neo X team will evaluate each submission individually, considering both technical and strategic fit.