UnVaultDeveloper Docs
Smart contracts

Contract addresses

The protocol contracts are owned and administered by UV Tech Foundation. The canonical registry is the configuration the Unvault app itself reads, published as JSON at GET https://api.unvault.com/api/chains (public, no API key). This page mirrors that registry and is updated whenever a contract is deployed, upgraded or retired. A Chains page inside the app showing the same registry is PLANNED. Treat any address that does not appear in the registry as unverified, whatever its source.

Do not copy an address across chains. The deployer's transaction nonces diverged between chains, so the same address serves a different role on different chains — for example 0x081ffaf785040219ca8b1c7424b72ba20844bb38 is the auction on Ethereum, Polygon and ApeChain but the signed zone on BNB Chain, Abstract and Robinhood Chain. Always read the row for the chain you are on.

Administration#

Every protocol contract that has an owner or admin is controlled by the Foundation's multisig, a Safe deployed at the same address on all seven chains. The signed zone, auction and cross-chain purchase executor use two-step ownership (owner() / pendingOwner()); the LayerZero sender exposes admin(); the LayerZero receiver and the fee oracle use single-step ownership; the royalty registry has no owner. Control of every contract was transferred from the deployment key to the multisig on 2026-10-05.

Marketplace contracts (live)#

Deployed 2026-09-20 to 2026-09-21. Settlement runs through the Seaport 1.6 protocol with the Unvault signed zone validating orders and applying the 0.5% marketplace fee and creator earnings; the auction contract runs English and Dutch auctions (auctions are PLANNED in the app); the royalty registry holds per-collection creator-earnings splits; the cross-chain purchase executor settles purchases paid from another chain.

ChainSigned zone (UnVaultSignedZone)Auction (UnVaultAuction)Royalty registry (UnVaultRoyaltyRegistry)Cross-chain purchase executor (CrossChainPurchaseExecutor)
Ethereum (1)0xe4e72ac12af07fa4e217157d9768b6c6f651928d0x081ffaf785040219ca8b1c7424b72ba20844bb380x94b55e010a17cba631a9235de19ce65bdc5cced30xd5ce8db849d878d2a0d954a36b2ed93e15d32206
Base (8453)0x0b189350c7025f134a5a327086c8df823a1ff5970xd5ce8db849d878d2a0d954a36b2ed93e15d322060x34b1b4798c0e93b296759efcf7f0ea5f4da98d570xc2b9f29b513f872e312b67fc575159e296d63535
ApeChain (33139)0xe4e72ac12af07fa4e217157d9768b6c6f651928d0x081ffaf785040219ca8b1c7424b72ba20844bb380x94b55e010a17cba631a9235de19ce65bdc5cced30xd5ce8db849d878d2a0d954a36b2ed93e15d32206
Robinhood Chain (4663)0x081ffaf785040219ca8b1c7424b72ba20844bb380x160fc298d51be36aa59ca3b15f7e12614d50f3bd0x213ccd5a4036084cc8397b67c86fd1e431f794f80x70a1352252ce013e9603df2a88d2bebf003f7885
Polygon (137)0xe4e72ac12af07fa4e217157d9768b6c6f651928d0x081ffaf785040219ca8b1c7424b72ba20844bb380x94b55e010a17cba631a9235de19ce65bdc5cced30xd5ce8db849d878d2a0d954a36b2ed93e15d32206
BNB Chain (56)0x081ffaf785040219ca8b1c7424b72ba20844bb380x160fc298d51be36aa59ca3b15f7e12614d50f3bd0x213ccd5a4036084cc8397b67c86fd1e431f794f80x70a1352252ce013e9603df2a88d2bebf003f7885
Abstract (2741)0x081ffaf785040219ca8b1c7424b72ba20844bb380x160fc298d51be36aa59ca3b15f7e12614d50f3bd0x213ccd5a4036084cc8397b67c86fd1e431f794f80x70a1352252ce013e9603df2a88d2bebf003f7885

Omnichain contracts (live; vault moves are PLANNED in the app)#

Deployed 2026-09-25. The omnichain factory deploys and registers a collection's contracts on other chains (its Echo contracts); the LayerZero sender and receiver carry the vault messages between chains; the bridge fee oracle prices the vault fee in the chain's native currency using a price feed.

ChainLayerZero EIDOmnichain factory (OmnichainFactoryProxy)LayerZero sender (OmnichainLZSender)LayerZero receiver (OmnichainLZReceiver)Bridge fee oracle (BridgeFeeOracle)
Ethereum (1)301010xD27e3Cb5D673009C771919F6D61A39Da6F4168600xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70xB5322bF1c2Bb2c6FA5445E3F486581d1e9567E810x9DDa74121EB12f1F49934fbAb9585408D57d7ddb
Base (8453)301840x092F7ae18c53fF20bC02dAfFe240934514A583AD0x7A22E1DeA8f1A17382986F7492f6084fE1C265850xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70x0738F5D970c59D3CbF8c66fCEbb228D06a50998B
ApeChain (33139)303120xD27e3Cb5D673009C771919F6D61A39Da6F4168600xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70xB5322bF1c2Bb2c6FA5445E3F486581d1e9567E810x9DDa74121EB12f1F49934fbAb9585408D57d7ddb
Robinhood Chain (4663)304160xD27e3Cb5D673009C771919F6D61A39Da6F4168600xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70xB5322bF1c2Bb2c6FA5445E3F486581d1e9567E810x9DDa74121EB12f1F49934fbAb9585408D57d7ddb
Polygon (137)301090x092F7ae18c53fF20bC02dAfFe240934514A583AD0x7A22E1DeA8f1A17382986F7492f6084fE1C265850xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70x97ce92dC1A119db82E3f57CE3bF88B5ff3bCE554
BNB Chain (56)301020xD27e3Cb5D673009C771919F6D61A39Da6F4168600xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70xB5322bF1c2Bb2c6FA5445E3F486581d1e9567E810x9DDa74121EB12f1F49934fbAb9585408D57d7ddb
Abstract (2741)303240x092F7ae18c53fF20bC02dAfFe240934514A583AD0x7A22E1DeA8f1A17382986F7492f6084fE1C265850xb1D0FC08d48366F02a8Ccd06F228101f45aeF0C70x97ce92dC1A119db82E3f57CE3bF88B5ff3bCE554

Third-party contracts the protocol depends on#

These are not Unvault or Foundation contracts and are documented by their own projects: the LayerZero endpoint on each chain, the Seaport 1.6 settlement protocol and OpenSea's signed zone and conduit (used to fill orders from other venues), and the wrapped-native and USDC tokens used for offers and token-priced listings. The transfer validator used by creator-token collections is Limit Break's CreatorTokenTransferValidator at 0x721C008fdff27BF06E7E123956E2Fe03B63342e3 on every EVM chain (see Standards and interfaces).

ChainLayerZero endpointSeaport 1.6OpenSea signed zoneOpenSea conduitWrapped native (WETH / WAPE / WPOL / WBNB)USDC
Ethereum (1)0x1a44076050125825900e736c501f859c50fE728c0x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd1000x1e0049783f008a0085193e00003d00cd54003c710xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc20xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
Base (8453)0x1a44076050125825900e736c501f859c50fE728c0x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd1000x1e0049783f008a0085193e00003d00cd54003c710x42000000000000000000000000000000000000060x833589fcd6edb6e08f4c7c32d4f71b54bda02913
ApeChain (33139)0x6F475642a6e85809B1c36Fa62763669b1b48DD5B0x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd1000x1e0049783f008a0085193e00003d00cd54003c710x48b62137edfa95a428d35c09e44256a739f6b557—
Robinhood Chain (4663)0x6f475642a6e85809b1c36fa62763669b1b48dd5b0x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd100—0x0bd7d308f8e1639fab988df18a8011f41eacad73—
Polygon (137)0x1a44076050125825900e736c501f859c50fE728c0x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd1000x1e0049783f008a0085193e00003d00cd54003c710x0d500b1d8e8ef31e21c99d1db9a6444d3adf12700x3c499c542cef5e3811e1192ce70d8cc03d5c3359
BNB Chain (56)0x1a44076050125825900e736c501f859c50fE728c0x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd1000x1e0049783f008a0085193e00003d00cd54003c710xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d
Abstract (2741)0x5c6cfF4b7C49805F8295Ff73C204ac83f3bC4AE70x0000000000000068f116a894984e2db1123eb3950x000056f7000000ece9003ca63978907a00ffd100—0x3439153eb7af838ad19d56e1571fbd09333c28090x84a71ccd554cc1b02749b35d22f684cc8ec987e1

Not yet deployed (PLANNED)#

The registry has no entries yet for the pool factory and pool template (liquidity pools), the vault, escrow and launchpad minter contracts, token metadata, or the DIVIT contracts (DIVIT pool, gacha factory, payment distributor and eligibility). They will be listed here when they are deployed.

Verifying a genuine contract#

  1. Compare the address with the registry at GET https://api.unvault.com/api/chains for the chain you are on.
  2. Check that the source is verified on the chain's block explorer under the contract name shown in the tables above.
  3. Confirm that owner() (or admin() on the LayerZero sender) is a multisig contract — the same one on every protocol contract and on every chain — and not an externally owned account.

Public third-party protocols the contracts call — the Seaport settlement protocol and LayerZero endpoints — are not Unvault or Foundation contracts and are documented by their own projects.

Markdown version: /contract-addresses.md · llms.txt · Use of the APIs is governed by the Terms of Service, Section 21.