Smart contracts
Contract addresses
The protocol contracts are owned and administered by UV Tech Foundation. The canonical address registry is published in two places, and only two:
- The Chains page inside the Unvault app, which reads the live configuration the app itself uses.
GET /chainson the API, which returns the same configuration as JSON.
This page mirrors that registry for each chain and is updated whenever a contract is deployed, upgraded or retired. Treat any address that does not appear in the registry as unverified, whatever its source.
Contract set per chain#
| Contract | Role |
|---|---|
| Settlement zone | Validates Unvault-signed marketplace orders for the Seaport settlement protocol and applies the 0.5% marketplace fee and creator earnings |
| Auction | English and Dutch auctions |
| Royalty registry | On-chain creator-earnings splits per collection |
| Transfer validator | Operator allow-listing for creator-earnings enforcement (Limit Break validator, v5) |
| Pool factory and pool template | Deploys and implements BUY / SELL / TRADE liquidity pools |
| DIVIT pool and gacha | Receives creator earnings and distributes holder rewards, the Minter's Bonus, and gacha cycles |
| Launchpad collection implementation | ERC-721AC collections deployed by creators |
| Vault adapter and escrow | Locks originals, mirrors canonical instances, and carries LayerZero messages |
| Fee recipient | Receives the marketplace, launchpad, swap and vault fees listed in the Fee Schedule |
Verifying a genuine contract#
- Compare the address with the Chains page and
GET /chains. - Check that the source is verified on the chain's block explorer.
- Confirm the owner or admin role on the explorer resolves to the Foundation's published administrative address for that chain, as listed in the registry.
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.