DOCUMENTATION

Bridge Integration

Integrate the Onyx bridge without hardcoding mutable limits or operator addresses.

Documentation

Tokenomics

The Onyx bridge moves XCN, ETH, and USDC between Ethereum Mainnet and Onyx Mainnet.

InterfaceURL
User interfacehttps://app.onyx.org/bridge
REST APIhttps://bridgeapi.onyx.org/api/v1
Ethereum BridgeLock0xa9fd64b5095d626f5a3a67e6db7fb766345f8092
Onyx BridgeMint0x1d14ae13ca030eb5e9e2857e911af515cf5ffff2

Integration rules

  • Call GET /health before enabling a bridge action.
  • Fetch GET /bridge/limits and a fee quote immediately before presenting or submitting a transfer.
  • Poll GET /bridge/status using the source transaction hash and surface the returned status truthfully.
  • Treat maintenance or delayed states as unavailable/in-progress, not as success.
  • For native XCN from Onyx to Ethereum, register the signed intent first and send only to the destination returned by that response.
  • ERC-1271 signatures from deployed smart accounts are supported. For ERC-4337, bind the final execution transaction hash, not the user-operation hash.

Processing time depends on source-chain confirmation, relayer state, security holds, and destination submission. Applications must use API state instead of promising a fixed duration.

See the REST API Reference, Smart Account Integration, and contract registry.