Thanos Smart Contracts
This package contains the L1 and L2 contracts and components to build the Thanos. We can use ERC20 token as L2 native token after modifying configuration in deploy-config.
Directory Structure
├── deploy-config: Pre-defined deployment configuration on each network
├── deployments: Information about the contracts deployed on each network
├── genesis: Deployed contract address list, L2 Genesis file, Rollup configuration on each network
├── uniswap-v3-artifacts: Hardhat artifacts for Uniswap V3
├── invariant-docs: Documentation for all defined invariant tests
├── lib: External libraries with Git submodules
├── scripts: Deploy Scripts
├── src: Contracts
│ ├── L1: Contracts deployed on the L1
│ ├── L2: Contracts deployed on the L2
│ ├── cannon: Contracts for cannon
│ ├── dispute: Contracts for dispute game
│ ├── libraries: Libraries
│ │ └── Predeploys.sol: Pre-deployed contract addresses on L2 Genesis
│ ├── tokamak-contracts
│ │ └── USDC: Contract for USDC bridge
│ └── universal: Universal contracts
├── test: Contracts for unit test
├── foundry.toml: Foundry configuration
├── hardhat.config.ts: Hardhat configuration
...
Contracts Overview
Contracts deployed to L1
Contracts deployed to L2
Installation
We export contract ABIs, contract source code, and contract deployment information for this package via pnpm
:
pnpm install @tokamak-network/thanos-contracts
Build
We can build the package in the monorep using pnpm
# Install dependencies
pnpm install
# Compile the contracts and make artifacts
pnpm build
Test
We are able to run unit tests for all contracts within the package. The files used for testing are located in the test directory. Please refer to Test Options for more forge test
options.
# Run the unit test all contracts in this package
pnpm test
# Run the unit test for specific contract
forge test --match-contract <contract-name>
Deployment
The smart contracts are deployed using foundry
with a hardhat-deploy
compatibility layer. When the contracts are deployed,
they will write a temp file to disk that can then be formatted into a hardhat-deploy
style artifact by calling another script.
Configuration
Create or modify a file <network-name>.json
inside of the deploy-config
folder.
By default, the network name will be selected automatically based on the chainid. Alternatively, the DEPLOYMENT_CONTEXT
env var can be used to override the network name.
The IMPL_SALT
env var can be used to set the create2
salt for deploying the implementation contracts.
Execution
- Set the env vars
ETH_RPC_URL
, PRIVATE_KEY
and ETHERSCAN_API_KEY
if contract verification is desired - Deploy the contracts with
forge script -vvv scripts/Deploy.s.sol:Deploy --rpc-url $ETH_RPC_URL --broadcast --private-key $PRIVATE_KEY
Pass the --verify
flag to verify the deployments automatically with Etherscan. - Generate the hardhat deploy artifacts with
forge script -vvv scripts/Deploy.s.sol:Deploy --sig 'sync()' --rpc-url $ETH_RPC_URL --broadcast --private-key $PRIVATE_KEY
Deploying a single contract
All of the functions for deploying a single contract are public
meaning that the --sig
argument to forge script
can be used to
target the deployment of a single contract.
Static Analysis
contracts-bedrock
uses slither as its primary static analysis tool. Slither will be run against PRs as part of CI, and new findings will be reported as a comment on the PR.