Skip to content

Latest commit

 

History

History
88 lines (59 loc) · 6.54 KB

DEPLOY.md

File metadata and controls

88 lines (59 loc) · 6.54 KB
Raw

Deploying Atlas

This is a guide to getting the Atlas smart contracts deployed on an EVM chain.

Atlas Deployment Process

  1. Checkout to this commit hash on the main branch. This was the commit hash represents the state of the codebase at the time that the Spearbit audit was finalized.
git checkout dca0b9946e8f59347610cd24a0bca5e84ddea00e
  1. Set up your .env file with the variables relevant to the chain to which you are trying to deploy. Note: the GOV_PRIVATE_KEY is the private key to the public address from which the contracts will be deployed. Check out the Wallet List docs if in doubt about which address to deploy from.
MAINNET_RPC_URL=https://eth-mainnet.g.alchemy.com/v2/XXXXXXXXXXXXXXXXXXXX
SEPOLIA_RPC_URL=https://eth-sepolia.g.alchemy.com/v2/XXXXXXXXXXXXXXXXXXXX
AMOY_RPC_URL=https://polygon-amoy.g.alchemy.com/v2/XXXXXXXXXXXXXXXXXXXX
POLYGON_RPC_URL=https://polygon-mainnet.g.alchemy.com/v2/XXXXXXXXXXXXXXXXXXXX
ETHERSCAN_API_KEY=XXXXXXXXXXXXXXXXXXXX
POLYGONSCAN_API_KEY=XXXXXXXXXXXXXXXXXXXX

GOV_PRIVATE_KEY=0x123456789...
  1. Run the deployment script in simulation mode to verify everything works. Note: exclude the --broadcast flag to run the script in simulation mode. See Foundry's script command options.
source .env && forge script script/deploy-atlas.s.sol:DeployAtlasScript --rpc-url ${POLYGON_RPC_URL} --legacy
  1. Run the deployment script again, this time in broadcast mode to actually send the transactions to deploy the contracts. Note: include the --broadcast flag to run the script in broadcast mode. We also include --etherscan-api-key ${POLYGONSCAN_API_KEY} --verify to verify the contracts on Polygonscan.
source .env && forge script script/deploy-atlas.s.sol:DeployAtlasScript --rpc-url ${POLYGON_RPC_URL} --legacy --broadcast --etherscan-api-key ${POLYGONSCAN_API_KEY} --verify

If all goes well, the script will output the addresses of the deployed contracts, and handle verification through Etherscan or Polygonscan automatically. These addresses will also be saved in the deployments.json file. NOTE: the chain in deployments.json is detected using block.chainid, and is thus dependent on specifying the correct --rpc-url when running the deployment script.

DAppControl Deployment Process

Coming soon...

Latest Deployments

Polygon Amoy Testnet

Commit hash of deployment: dca0b99

Contract Address
Atlas 0x282BdDFF5e58793AcAb65438b257Dbd15A8745C9
AtlasVerification 0x3b7B38362bB7E2F000Cd2432343F3483F785F435
Simulator 0x3efbaBE0ee916A4677D281c417E895a3e7411Ac2
Sorter 0xa55051bd82eFeA1dD487875C84fE9c016859659B
DAppControl Address
FastLane Online 0xf0E388C7DFfE14a61280a4E5b84d77be3d2875e3

Polygon Mainnet

Commit hash of deployment: e99082f

Contract Address
Atlas 0x912AceADa1b9c9B378894D0610C5684167710FDD
AtlasVerification 0x2fBF38a38D753E4ce398000CCC552Efa50702e1e
Simulator 0x1244E4B8D93D2A72692Bf3600f7f5a494e24895a
Sorter 0xFac7bf300E7eb17A2eD0Be67b60f5FeDd2E28E90
DAppControl Address
FastLane Online 0x498aC70345AD6b161eEf4AFBEA8F010401cfa780

Binance Smart Chain Mainnet

Commit hash of deployment: 3416300

Contract Address
Atlas 0xD72D821dA82964c0546a5501347a3959808E072f
AtlasVerification 0xae631aCDC436b9Dfd75C5629F825330d91459445
Simulator 0xAb665f032e6A20Ef7D43FfD4E92a2f4fd6d5771e
Sorter 0xb47387995e866908B25b49e8BaC7e499170461A6