Neo X smart contracts can now request and receive external data through Neo N3’s built-in oracle service, following the launch of the Neo Oracle Gateway by BaneLabs. The new infrastructure component routes oracle requests across chains using the Message Bridge and is deployed on both MainNet and TestNet.
The release marks an effort to extend Neo N3’s native capabilities to its EVM-compatible sidechain. The development team has sought to bring proven Neo N3 features into Neo X’s EVM environment, and this release represents a step in that direction.
What the Oracle Gateway enables
The gateway establishes a pattern for Neo X to access Neo N3’s native services through the Message Bridge, which launched in Dec. 2025. While the bridge was initially used for asset transfers between the two chains, the Oracle Gateway demonstrates it can also route service calls, allowing Neo X contracts to invoke Neo N3 features and receive results without leaving the EVM environment.
In the case of the oracle, this means Neo X applications can access off-chain data through Neo N3’s established oracle service, which has been operating in production since 2021. DeFi protocols can retrieve price feeds, dApps can query external APIs, and smart contracts can verify conditions that exist outside the blockchain, all by routing requests through Neo N3 rather than relying on a new oracle built from scratch on Neo X.
The same bridge-based pattern could be applied to other Neo N3 features and contract services in the future, effectively making Neo N3’s ecosystem of native capabilities available to Neo X developers.
How the Oracle Gateway works
The Neo Oracle Gateway operates through a request-response flow built on the Message Bridge, the cross-chain communication layer Neo launched to connect Neo X and Neo N3.
When a Neo X smart contract needs external data, the process works as follows:
- The contract submits an Oracle request via the Message Bridge
- Neo N3 receives the request and executes it using its native oracle, which fetches the specified external data
- The oracle result returns through the Message Bridge to Neo X
- The originating contract receives the response and continues execution
Neo X contracts interact with the gateway through the IOracleProxy interface, calling initiateOracleCall() with a serialized request containing a URL, a JSONPath filter to extract specific data from the response, and a callback method name. Results can be retrieved using getOracleResult() or checked for existence with hasOracleResult().
A Watchtower service, an off-chain monitoring component, tracks bridge transactions on both chains and can handle message execution automatically, reducing the manual overhead for developers.
3vm inspection tool
Alongside the Oracle Gateway, AxLabs released 3vm, a companion tool for inspecting and debugging the Message Bridge. Available at 3vm.axlabs.net, the tool is designed for developers, including AI agents, to monitor bridge status and trace cross-chain transactions.
3vm can also be used to test the Oracle Gateway end-to-end: users connect a wallet, select a REST API, submit a request from Neo X, and observe the result returned on-chain.
Developer resources
The gateway contracts are open source under the Bane Labs GitHub organization. Bane Labs is the collaborative development entity behind Neo X, comprising Neo Global Development, AxLabs, and Neo SPCC. The Neo N3 side is implemented in Java using neow3j v3.24.0, while the Neo X side is written in Solidity with Hardhat. Both repositories carry v0.0.1 releases.
Contract addresses are identical on MainNet and TestNet:
- Neo N3:
0x5a0a0f188f2582ad60c1970267df30ec5428100d - Neo X:
0xce6138E61e5727a318D0DebEaD99Aff24B929131
Developers can construct serialized oracle calls using the @bane-labs/bridge-sdk-ts TypeScript package or the neo-serializer-evm Solidity library.
The full documentation can be found at the link below:
https://xdocs.ngd.network/integrations/oracles/neo-oracle-gateway