Deployed contracts
A list of deployed Tableland registry contracts for each supported chain.
The following page highlights which chains Tableland has smart contracts deployed on, which is currently Ethereum and a subset of its scaling solutions. Over time, additional EVM compatible chains will be added based on developer demand.
Registry contract
The TablelandTables registry contract exists on each of the chains below and is generally responsible for creating (minting) tables, SQL write statements, and access controls. Each chain has its associated name, environment, chain ID, and the contract address (links to a block explorer) displayed.
| Chain | Environment | Chain ID | Address |
|---|---|---|---|
| ethereum | mainnet | 1 | 0x012969f7e3439a9B04025b5a049EB9BAD82A8C12 |
| optimism | mainnet | 10 | 0xfad44BF5B843dE943a09D4f3E84949A11d3aa3e6 |
| arbitrum one | mainnet | 42161 | 0x9aBd75E8640871A5a20d3B4eE6330a04c962aFfd |
| arbitrum nova | mainnet | 42170 | 0x1A22854c5b1642760a827f20137a67930AE108d2 |
| base | mainnet | 8453 | 0x8268F7Aba0E152B3A853e8CB4Ab9795Ec66c2b6B |
| polygon | mainnet | 137 | 0x5c4e6A9e5C1e1BF445A062006faF19EA6c49aFeA |
| filecoin | mainnet | 314 | 0x59EF8Bf2d6c102B4c42AEf9189e1a9F0ABfD652d |
| ethereum sepolia | testnet | 11155111 | 0xc50C62498448ACc8dBdE43DA77f8D5D2E2c7597D |
| optimism sepolia | testnet | 11155420 | 0x68A2f4423ad3bf5139Db563CF3bC80aA09ed7079 |
| arbitrum sepolia | testnet | 421614 | 0x223A74B8323914afDC3ff1e5005564dC17231d6e |
| base sepolia | testnet | 84532 | 0xA85aAE9f0Aec5F5638E5F13840797303Ab29c9f9 |
| polygon amoy | testnet | 80002 | 0x170fb206132b693e38adFc8727dCfa303546Cec1 |
| filecoin calibration | testnet | 314159 | 0x030BCf3D50cad04c2e57391B12740982A9308621 |
| local tableland | local-only nodes | 31337 | 0xe7f1725e7734ce288f8367e1bb143e90bb3f0512 |
Tableland is still in open beta and will be launching the production network in 2024. But, smart contracts and apps deployed on testnet and mainnet chains can and should use the Tableland during the open beta period.
Developers should still proceed with caution due to the nature of open beta changes and ensure contracts that use Tableland are future-proof.