Networks and contracts¶
The tables below are generated during the documentation build from networks/network-ids.json and nexa-mainnet-v6.json. They are a readable projection, not a separate deployment registry.
Canonical Mainnet V6 projection¶
Supported networks¶
| Network | Chain ID | Network ID | Published routes | State | Verification |
|---|---|---|---|---|---|
| Base | 8453 | 0x3d5484ad492110227dc184ab6abbeeccd54b127aa00bfc256fd8d8037a4e48c2 | 108 | Active | Evidence |
| BNB Smart Chain | 56 | 0x5863eb850b94ec5a94a1653871dc308d32f4aec504d789f356419886170a0928 | 126 | Active | Evidence |
| HyperEVM | 999 | 0x5587698f40d78ef64484dda8f2c78692af870cfe3926dbc61a73881680bd01c8 | 108 | Active | Evidence |
Solver-facing contracts¶
| Contract | Address | Runtime code hash | ABI source |
|---|---|---|---|
NexaMainnetRegistryV6 | 0x3db7752f052ACFECB3DA99BeE7c6a34D22367141 | 0x5e766be0eb7a9b75f0b38c8509a15ac261209f06b0c993e8904a9f38633c790a | ./abi/solver-facing.json#/contracts/NexaMainnetRegistryV6 |
NexaMainnetRouterV6 | 0x9eA675a496b6a2D13B3091F6e6eB3f87183C3938 | 0xcdda1b571b317479c6d297aa4354c406d4709f83562e2b6b29bd0e1268e4af70 | ./abi/solver-facing.json#/contracts/NexaMainnetRouterV6 |
NexaSolverDiscoveryV6 | 0x7942d9FcC6cCe078de6a226aDEAbf96C89a46CB6 | 0x57cb853a995215d352eb64ab9ec33aed60f4ef5f8a38575bc2dd018b38babfc1 | ./abi/solver-facing.json#/contracts/NexaSolverDiscoveryV6 |
ERC-7683 module | 0x534A0f500A7270b9b19d2AFa18DE24DCE93eb522 | 0xea99f0e1e33a9a9e1ae926e8f15fd09bf1b7b9cecf81a2ef294cd4820e26d392 | standards/nexa-standards.json |
OIF module | 0x4f81426fE8999E982aE6b771536a4093879F6A20 | 0x103c954e71ec79abefc0f8e1ef745787649edb91742a4d4a7b0d2a4646925cba | standards/nexa-standards.json |
Release ID: 0xcc0dc051739f2dafaebd2eb5663937850dcc3e7951e38f437e00fcd9fa6c8ff6. Addresses marked as the same across chains are still verified independently on each chain.
How to verify a deployment¶
For every chain you intend to use:
- Fetch the canonical passive on-chain fingerprint from the discovery manifest.
- Require the expected chain ID, release ID, addresses, runtime code hashes, selectors, and same-address evidence.
- Read the Discovery Facade and compare its Registry, Router, release, deployment version, chain ID, live state, and discovery URI.
- Compare deployed runtime bytecode hashes with the canonical fingerprint.
- Check the linked explorer and Sourcify evidence where supported.
These are read-only checks. They submit no transaction.
Contract roles¶
Discovery Facade¶
The solver-facing Facade exposes the release and deployment identity, canonical discovery URI, Registry and Router bindings, route enumeration, and live system state. It is the smallest on-chain discovery entry point.
Registry¶
The Registry is authoritative for registered networks, assets, routes, execution generations, and executable route state. External index data must be reconciled against it before execution.
Router¶
The Router verifies and consumes the issued permit through fillDirect and emits the source-fill event. A successful integration calls it once on the source chain.
Standards modules¶
The ERC-7683 module resolves an issued Nexa payload to the Router call through off-chain eth_call. The OIF module exposes discovery and deterministic mandate description only; it is not an alternate execution route.