JSPM

  • Created
  • Published
  • Downloads 235
  • Score
    100M100P100Q94534F
  • License MIT AND Apache-2.0

Tableland Tables EVM contracts and client components

Package Exports

  • @tableland/evm
  • @tableland/evm/proxies.js
  • @tableland/evm/typechain-types/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@tableland/evm) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@tableland/evm

GitHub license GitHub package.json version Release standard-readme compliant

Tests

Tableland Tables EVM contracts and client components

Table of Contents

Background

This is the Tableland Tables EVM contracts and client components.

Currently supported chains

Chain Chain ID Contract
Goerli 5 0xDA8EA22d092307874f30A1F277D1388dca0BA97a
Optimistic Kovan 69 0xf2C9Fc73884A9c6e6Db58778176Ab67989139D06
Polygon Mumbai 80001 0x4b48841d4b32C4650E4ABc117A03FE8B51f38F68

Development

Building the client

You can build the Typescript client locally:

npm install
npx hardhat compile
npm run build

Testing

Run the test suite:

npm test

Test with gas reporting:

REPORT_GAS=true npx hardhat test

Deploying

Deployments are handled on a per-network basis:

npx hardhat run scripts/deploy.ts --network optimism

Network names may include context for the target Tableland network:

npx hardhat run scripts/deploy.ts --network optimism-kovan-staging

Where optimism-kovan-staging indicates a deployment to the Optimism Kovan testnet for the Tableland staging network.

Refer to the proxies entry in hardhat.config.js for the list of current deployments.

Upgrading

The Tableland contracts are currently upgradeable at this early stage of development. Upgrades are handled much like deployments:

npx hardhat run scripts/upgrade.ts --network optimism

Upgrading on a network only works if a previous deployment already exists, referenced by a corresponding proxy address in the proxies entry in hardhat.config.js.

Extacting the ABI and Bytecode

You can you grab the assets you need by compiling and then using some jq magic:

ABI

cat artifacts/contracts/TablelandTables.sol/TablelandTables.json | jq '.abi' > abi.json

Bytecode

cat artifacts/contracts/TablelandTables.sol/TablelandTables.json | jq -r '.bytecode' > bytecode.bin

Generate the Go client!

You can use the above abi.json to build the Go client:

mkdir gobuild
abigen --abi ./abi.json --bin ./bytecode.bin --pkg contracts --out gobuild/Registry.go

Etherscan verification

To perform Etherscan verification, you first need to deploy a contract to an Ethereum network that's supported by Etherscan, such as Goerli:

npx hardhat run scripts/deploy.ts --network ethereum-goerli

Then, copy the deployment address and paste it in to replace DEPLOYED_CONTRACT_ADDRESS in this command:

npx hardhat verify DEPLOYED_CONTRACT_ADDRESS --network ethereum-goerli

Speedier tests

For faster runs of your tests and scripts, consider skipping ts-node's type checking by setting the environment variable TS_NODE_TRANSPILE_ONLY to 1 in hardhat's environment. For more details see the documentation.

Contributing

PRs accepted.

Small note: If editing the README, please conform to the standard-readme specification.

License

MIT AND Apache-2.0, © 2021-2022 Tableland Network Contributors