Supported chains
Supported chains. The live configuration is the public registry at GET https://api.unvault.com/api/chains (an in-app Chains page showing the same registry is PLANNED):
| Chain | Chain ID | LayerZero EID | Native currency | Marketplace | Launchpad | Vault |
|---|---|---|---|---|---|---|
| Ethereum | 1 | 30101 | ETH | live (beta) | PLANNED | PLANNED |
| Base | 8453 | 30184 | ETH | live (beta) | PLANNED | PLANNED |
| ApeChain | 33139 | 30312 | APE | live (beta) | PLANNED | PLANNED |
| Robinhood Chain | 4663 | 30416 | ETH | live (beta) | PLANNED | PLANNED |
| Polygon | 137 | 30109 | POL | live (beta) | PLANNED | PLANNED |
| BNB Chain | 56 | 30102 | BNB | live (beta) | PLANNED | PLANNED |
| Abstract | 2741 | 30324 | ETH | live (beta) | PLANNED | PLANNED |
| Solana | — | — | SOL | PLANNED | PLANNED | — |
Launchpad and vault availability will be enabled per collection by its creator from Collection Manage once those features ship; a chain being supported does not mean every collection on it can be vaulted. The marketplace and omnichain contracts are already deployed on all seven EVM chains — see Contract addresses.
Chain identifiers in the API use lowercase slugs: ethereum, base, apechain, robinhood, polygon, bnb, abstract. The registry endpoint returns numeric chain IDs with the chain name, native symbol and LayerZero endpoint ID.
Chain IDs above are the public network IDs and should be verified against the chain's own documentation before use.
Markdown version: /supported-chains.md · llms.txt · Use of the APIs is governed by the Terms of Service, Section 21.