Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Contract Addresses

Source of truth: config/deployed/ JSON files. This page is derived from those files. When in doubt, refer to config/deployed/mainnet/ and config/deployed/testnet/.

Mainnet

Shared Contracts

The Blocklist contract is deployed once per chain and shared by all zERC20 tokens on that chain.

Chain
Blocklist

Ethereum

0x847b6E2dBB28A3a163C6e0fcA9B0222b9C1E4Df9

Arbitrum

0x847b6E2dBB28A3a163C6e0fcA9B0222b9C1E4Df9

Base

0x847b6E2dBB28A3a163C6e0fcA9B0222b9C1E4Df9

BNB Chain

0x847b6E2dBB28A3a163C6e0fcA9B0222b9C1E4Df9

Polygon

0x847b6E2dBB28A3a163C6e0fcA9B0222b9C1E4Df9

Kaia

0x847b6E2dBB28A3a163C6e0fcA9B0222b9C1E4Df9

All chains share the same Blocklist address via CREATE3 deterministic deployment.

zETH

Hub: 0x6B5e8509ae57A54863A7255e610d6F0c10FCAFB5 (Base)

Ethereum

Contract
Address

zERC20

0x410056c6F0A9ABD8c42b9eEF3BB451966Fb0d924

Verifier

0xdCC76DEbb526Eef0210Bd38729b803591951Ab34

LiquidityManager

0xcC10b7098FEf1aB2f0FF3bE91d2A7B3230b90CF0

Adaptor

0xfDe2C5758BbdDcDEa2d73EdeB5C13DE98B21Eb7D

Arbitrum

Contract
Address

zERC20

0x410056c6F0A9ABD8c42b9eEF3BB451966Fb0d924

Verifier

0xdCC76DEbb526Eef0210Bd38729b803591951Ab34

LiquidityManager

0xcC10b7098FEf1aB2f0FF3bE91d2A7B3230b90CF0

Adaptor

0xfDe2C5758BbdDcDEa2d73EdeB5C13DE98B21Eb7D

Base

Contract
Address

zERC20

0x410056c6F0A9ABD8c42b9eEF3BB451966Fb0d924

Verifier

0xdCC76DEbb526Eef0210Bd38729b803591951Ab34

LiquidityManager

0xcC10b7098FEf1aB2f0FF3bE91d2A7B3230b90CF0

Adaptor

0xfDe2C5758BbdDcDEa2d73EdeB5C13DE98B21Eb7D

zUSDC

Hub: 0x0E81e4CF6C8B408bC40D7AC8240bBc12CdD56F1D (Base)

Ethereum

Contract
Address

zERC20

0xEB81ab55Bc7aa89d1e0E3F60597D86e37702Af53

Verifier

0xfb786B5E6520284Aa6a8dFA3B4F7A09ed423e25f

LiquidityManager

0x04be137Df79bE7B5F3314C4a84D1C5E0d99BD477

Adaptor

0x3fCBc7f919b712258859e2e3c78188168E47B287

Arbitrum

Contract
Address

zERC20

0xEB81ab55Bc7aa89d1e0E3F60597D86e37702Af53

Verifier

0xfb786B5E6520284Aa6a8dFA3B4F7A09ed423e25f

LiquidityManager

0x04be137Df79bE7B5F3314C4a84D1C5E0d99BD477

Adaptor

0x3fCBc7f919b712258859e2e3c78188168E47B287

Base

Contract
Address

zERC20

0xEB81ab55Bc7aa89d1e0E3F60597D86e37702Af53

Verifier

0xfb786B5E6520284Aa6a8dFA3B4F7A09ed423e25f

LiquidityManager

0x04be137Df79bE7B5F3314C4a84D1C5E0d99BD477

Adaptor

0x3fCBc7f919b712258859e2e3c78188168E47B287

zBNB

Hub: 0x35eE54CEDb9aba3b785C493C0B50643E65471c7A (BNB Chain)

BNB Chain

Contract
Address

zERC20

0x4388D5618B9e13Bd580209CDf37a202778C75c54

Verifier

0xb05977Af4aA54117910ed72141F674531894774A

LiquidityManager

0x39Cc069dF606c7bc8c79b0ADd0696BCaf548eFD9

Adaptor

—

Note: zBNB wrap/unwrap is only available on BNB Chain. Other chains support zBNB transfers via LayerZero OFT but do not have LiquidityManager contracts.

Ethereum

Contract
Address

zERC20

0x4388D5618B9e13Bd580209CDf37a202778C75c54

Verifier

0xb05977Af4aA54117910ed72141F674531894774A

LiquidityManager

—

Adaptor

—

Arbitrum

Contract
Address

zERC20

0x4388D5618B9e13Bd580209CDf37a202778C75c54

Verifier

0xb05977Af4aA54117910ed72141F674531894774A

LiquidityManager

—

Adaptor

—

Base

Contract
Address

zERC20

0x4388D5618B9e13Bd580209CDf37a202778C75c54

Verifier

0xb05977Af4aA54117910ed72141F674531894774A

LiquidityManager

—

Adaptor

—

zJPYC

zJPYC is deployed on Polygon and Kaia as independent local-mode deployments. It has no Hub-backed cross-chain route.

Polygon

Contract
Address

zERC20

0xd33Bed4Ae7Fe50107c532f63740B1bF2dabf2b30

Verifier

0x106807240D00916C0b1568f2A809f651B6701331

LiquidityManager

0x12609C3A7a1A212953417c90472cdcf034965a1C

Adaptor

—

SwapHelper

0xd94B44026c85C8E57F844c204FE9aDEd669aB393

Kaia

Contract
Address

zERC20

0xd33Bed4Ae7Fe50107c532f63740B1bF2dabf2b30

Verifier

0x106807240D00916C0b1568f2A809f651B6701331

LiquidityManager

0x12609C3A7a1A212953417c90472cdcf034965a1C

Adaptor

—

SwapHelper

0xd94B44026c85C8E57F844c204FE9aDEd669aB393

Polygon and Kaia use the same contract addresses through deterministic CREATE3 deployment, but their local-mode state and operations are chain-specific.

Testnet

Shared Contracts

Chain
Blocklist

Sepolia

0xC5D75395376f2535EC1B7F0F803C91E80C3845e0

Arbitrum Sepolia

0xC5D75395376f2535EC1B7F0F803C91E80C3845e0

OP Sepolia

0xC5D75395376f2535EC1B7F0F803C91E80C3845e0

Kairos

0xC5D75395376f2535EC1B7F0F803C91E80C3845e0

zETH

Hub: 0xD18b503B335656C05dC516366C0C8FD6e3b13856 (Base Sepolia)

Sepolia

Contract
Address

zERC20

0xADAb5CaB352fb1eBF24CD951de224f9e952C82Ed

Verifier

0xD19b79cE0C2821158aDBDEf9cC8c8D858c9ef0Cc

LiquidityManager

0x5a09Cc328fA6bB32f3d6fC54906106ddD49a2D7c

Adaptor

0x588F07b52E50E8600F654c63176818403F6E3EB6

Arbitrum Sepolia

Contract
Address

zERC20

0xADAb5CaB352fb1eBF24CD951de224f9e952C82Ed

Verifier

0xD19b79cE0C2821158aDBDEf9cC8c8D858c9ef0Cc

LiquidityManager

0x5a09Cc328fA6bB32f3d6fC54906106ddD49a2D7c

Adaptor

0x588F07b52E50E8600F654c63176818403F6E3EB6

OP Sepolia

Contract
Address

zERC20

0xADAb5CaB352fb1eBF24CD951de224f9e952C82Ed

Verifier

0xD19b79cE0C2821158aDBDEf9cC8c8D858c9ef0Cc

LiquidityManager

0x5a09Cc328fA6bB32f3d6fC54906106ddD49a2D7c

Adaptor

0x588F07b52E50E8600F654c63176818403F6E3EB6

Base Sepolia

Contract
Address

Hub

0xD18b503B335656C05dC516366C0C8FD6e3b13856

Hub only — no zERC20/Verifier/LiquidityManager/Adaptor contracts are deployed on this chain.

zUSDC

Hub: 0xF64Bd0a90120611b0c941e3eF546f2F82F1eaB44 (Base Sepolia)

Sepolia

Contract
Address

zERC20

0x132CeD517327C2aC5073ACEb9eCF1e7783feCbcF

Verifier

0xb199A85463Bc5c0009c058E80b8A0d3D5e0025D6

LiquidityManager

0xB9f41F93882c2ddC212a4EcC776BBd9D97D2F3C6

Adaptor

0xC14A0a1381e455f89a31eDB00F562F5a6F8780Ad

Arbitrum Sepolia

Contract
Address

zERC20

0x132CeD517327C2aC5073ACEb9eCF1e7783feCbcF

Verifier

0xb199A85463Bc5c0009c058E80b8A0d3D5e0025D6

LiquidityManager

0xB9f41F93882c2ddC212a4EcC776BBd9D97D2F3C6

Adaptor

0xC14A0a1381e455f89a31eDB00F562F5a6F8780Ad

OP Sepolia

Contract
Address

zERC20

0x132CeD517327C2aC5073ACEb9eCF1e7783feCbcF

Verifier

0xb199A85463Bc5c0009c058E80b8A0d3D5e0025D6

LiquidityManager

0xB9f41F93882c2ddC212a4EcC776BBd9D97D2F3C6

Adaptor

0xC14A0a1381e455f89a31eDB00F562F5a6F8780Ad

Base Sepolia

Contract
Address

Hub

0xF64Bd0a90120611b0c941e3eF546f2F82F1eaB44

Hub only — no zERC20/Verifier/LiquidityManager/Adaptor contracts are deployed on this chain.

zBNB

Hub: 0x1285C8F8B058171D9B2C5faC51E8D8D84D031188 (BNB Testnet)

Sepolia

Contract
Address

zERC20

0x28240ADC769046793a139b815dad6618b7Eb2499

Verifier

0xb0A159eBF38b8cb539DE40836176d46C717Ff0cd

LiquidityManager

—

Adaptor

—

Arbitrum Sepolia

Contract
Address

zERC20

0x28240ADC769046793a139b815dad6618b7Eb2499

Verifier

0xb0A159eBF38b8cb539DE40836176d46C717Ff0cd

LiquidityManager

—

Adaptor

—

OP Sepolia

Contract
Address

zERC20

0x28240ADC769046793a139b815dad6618b7Eb2499

Verifier

0xb0A159eBF38b8cb539DE40836176d46C717Ff0cd

LiquidityManager

0xD05c2d006841F08826c3C531CC1a0AF997846222

Adaptor

—

BNB Testnet

Contract
Address

zERC20

0x28240ADC769046793a139b815dad6618b7Eb2499

Verifier

0xb0A159eBF38b8cb539DE40836176d46C717Ff0cd

LiquidityManager

0xD05c2d006841F08826c3C531CC1a0AF997846222

Adaptor

—

zJPYC

zJPYC uses local-mode redeem and does not have a Hub-backed cross-chain route. Mainnet includes Polygon and Kaia, while testnet includes Polygon Amoy and Kairos as independent local-mode deployments.

Polygon Amoy

Contract
Address

zERC20

0xCB111e5Cfa6c9E36ef7CCbf1D7508E55166CDA18

Verifier

0x61F29490CD5Fb0dd2D7FAFeF39bb8b44b4c571AC

LiquidityManager

0xDBAa93cEB519f553c5A437c29B2A6BE3c0d3b914

Adaptor

—

SwapHelper

0xeA6FebeFd53C44E7ACF1A7bb62b261a8e6e3b8ea

Kairos

Contract
Address

zERC20

0xe5dcfe6f713a4c2ecc4479119a255b0adbc710b2

Verifier

0x9523ee75a4cbb265ff7282e862e084133380dafe

LiquidityManager

0x2640f93Eab6f800766f05615496BC4A49C01546A

Adaptor

—

SwapHelper

0xe21b1Ec742Ae2D1c434532236Cca25386454Ac37

Kairos token config prefers the public Kairos RPC (https://public-en-kairos.node.kaia.io) and keeps Alchemy Kairos as a fallback because Alchemy Kairos has shown intermittent backend indexing errors.

ICP Canister IDs

Stealth messaging layer for encrypted announcements and key derivation on the Internet Computer.

  • Key Manager — Derives identity-based encryption (IBE) keys via VetKD for recipients to decrypt stealth payloads

  • Storage — Persists encrypted announcements and signed invoices

Mainnet

Canister
Principal ID

Key Manager

ub5gn-myaaa-aaaah-qrs2a-cai

Storage

ug4az-baaaa-aaaah-qrs2q-cai

Testnet

Canister
Principal ID

Key Manager

3gshj-ayaaa-aaaac-a4wfq-cai

Storage

46fkw-kqaaa-aaaac-a5a3q-cai

PreviousICP Storage Spec
NextExternal Links

Last updated

Was this helpful?