Skip to main content

Contract registry

These deployments were checked on ZEL testnet, chain ID 9350, on 14 September 2026. They are an observed deployment snapshot, not a list of supported routes or a security audit. Recheck the chain registry and proxy implementations before use.

Testnet contracts

ComponentAddressDeployment blockSource verification
Bridge proxy0x89d5aa702960FD0aE868e21a26f1F419e29431ef48019Proxy and implementation verified
Swapper proxy0x9d56a6741bfBc2f49BaE8a69aF4955DBcd09DB1448612Proxy and implementation verified
AMM router0x509945dCDda4DCc056935fFeb5b4c30B723b966e48587Verified
AMM factory0xac6d9cc15746248f120985568B79d8AD27ad406248583Verified
ZANO representation / router wrapper0xa8837A67c88e4C74D903952C8275A831Bf52eb1548025Not verified

The Core chain registry identifies the Bridge proxy for chain 9350. Read-only contract calls confirm that the Swapper points to this Bridge and router, and that the router points to the listed factory and wrapper.

Token metadata

The Core token registry identifies the wrapper as ZANO. Its current on-chain metadata is still Wrapped Zel / wZel; the intended ticker is ZANO. This deployment mismatch remains to be corrected. Identify the asset by chain and address, not its ticker alone.

Proxy implementations and ABIs

The EIP-1967 implementation storage slots match the explorer records. Bind each implementation ABI to its proxy address; do not use the proxy constructor ABI for application calls.

Blockscout's contract pages provide verified source and ABIs. The same records are available through GET /api/v2/smart-contracts/{address}. Bridge and Swapper were compiled with Solidity 0.8.9, the router with 0.6.6, and the factory with 0.5.16.

Administrative boundaries

The verified Bridge restricts upgrades to its owner. Swapper upgrades require DEFAULT_ADMIN_ROLE, while the factory restricts pair creation through CREATE_PAIR_ROLE.

At the time of inspection, the Bridge owner and member zero of the Swapper and factory default-admin roles were 0xE425646Ac72E9a1425861e8Cfa6bB69B711BFAd4. This does not establish who controls that account or enumerate every role member.

Still to complete

The release manifest needs the deployed source revisions, complete authority and upgrade policy, and verified wrapper source. Supported tokens, pairs, routes, fees, and operational guarantees remain TBA. Contract presence alone does not establish them.

See Bridge contracts for the deposit interface and Bridge API for live configuration queries.