Tech BlogShowcase

Deployed Contracts

Deployed Contracts

Testnet & mainnet contract information.

The Tableland testnet is live and accessible on the following testnet and mainnet chains, and each corresponding Tableland smart contract (proxy) address is listed:

Chain
Chain ID
Smart Contract Address
Ethereum Mainnet
1
0x012969f7e3439a9B04025b5a049EB9BAD82A8C12
Optimism Mainnet
10
0xfad44BF5B843dE943a09D4f3E84949A11d3aa3e6
Polygon Mainnet
137
0x5c4e6A9e5C1e1BF445A062006faF19EA6c49aFeA
Arbitrum One
42161
0x9aBd75E8640871A5a20d3B4eE6330a04c962aFfd
Ethereum Goerli
5
0xDA8EA22d092307874f30A1F277D1388dca0BA97a
Optimism Goerli
420
0xC72E8a7Be04f2469f8C2dB3F1BdF69A7D516aBbA
Polygon Mumbai
80001
0x4b48841d4b32C4650E4ABc117A03FE8B51f38F68
Arbitrum Goerli
421613
0x033f69e8d119205089Ab15D340F5b797732f646b

⚠️
Tableland is still in open beta and will be launching the production network in 2023. 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.

The TABLE Token

For each of the contracts deployed above, a globally unique TABLE ERC721 token will be minted. Anyone can create and own a table. On-chain access controls can be established to make the table itself collaborative in nature, such as a shared ownership model where certain permissioned users can insert or update rows in the table itself.

At a minimum, a TABLE owner has permissions to do whatever they want with the table, such as inserting new rows, updating / deleting existing ones, or setting a table controller that manages table the access controls. For example, take a table minted on Ethereum:

The TABLE ERC721 token anatomy.
The TABLE ERC721 token anatomy.

To view the TABLE token itself, check out the deployed contracts on various block explorers or see the following NFT marketplaces:

← Previous

Limits