Neo has launched a message bridge on MainNet, introducing a new cross-chain communication layer between EVM-compatible networks Neo X and Neo N3. This infrastructure allows applications on either chain to exchange arbitrary data, trigger smart contract execution on the other side's network, and configure functionality across the environment.
The message bridge extends Neo's interoperability stack beyond the asset transfer already supported through the existing token bridge between Neo X and Neo N3. The development team said reliability, monitoring, and security will continue to be priorities as usage increases.
Expanding cross-chain functionality
Unlike token bridges, which are limited to moving assets, message bridges support arbitrary messages. These messages can execute contract logic on the destination chain, store data without execution, or return results back to the originating chain.
This design enables use cases such as accessing Neo N3's native Oracle from Neo X, interacting with NeoFS from EVM-based applications, and building custom fungible or non-fungible token bridges. More complex cross-chain workflows such as asynchronous requests, swaps, and multi-step interactions are also supported.
Neo X is developed by BaneLabs, a collaboration between Neo Global Development, Neo SPCC, and AxLabs. The team has previously delivered infrastructure upgrades including MEV resistance and a token bridge layer.
Architecture and security model
The Neo N3 – Neo X bridge uses a three-tier smart contract architecture deployed on each chain. This includes bridge management contracts for governance and role-based access control, message bridge contracts to handle cross-chain communications, and native or token bridge contracts for asset transfers.
Cross-chain operations are verified through a multi-signature verification model. Configurable validator thresholds require the withdrawal root to be approved before execution using separate cryptographic key types used by the Neo N3 and EVM chains. The system uses a rolling Merkle route to track deposits and withdrawals and reduces gas costs through batch operations.
Security features include strict role separation, fine-grained suspension controls, and message execution windows.
Typescript SDK
In parallel with the MainNet rollout, BaneLabs has released several open source repositories to support integration. These include smart contracts for both EVM and Neo environments, TypeScript SDKs for front-end and back-end applications, and sample projects that demonstrate message execution and result processing across the chain.
The SDK lowers the barrier for EVM developers to build cross-chain applications by abstracting Neo N3's stack-based contract calls and managing encoding differences between the two environments.
The full announcement can be viewed from the link below.
https://neo.org/blog/details/4329
