Prerequisites
The following are the prerequisites you need to ensure before you start deploying the chain.
Funding Requirements
L1 RPC Endpoint
Beacon RPC Endpoint
AWS IAM account
(Optional) Operators can stake TON to earn seigniorage rewards
Tools
Let's go step by step about each of them.
1. Funding Requirements
Funding for multiple EOA accounts is a critical aspect of network setup and operation. These costs can be categorized into deployment costs and post-deployment operational costs.
Operator account
The operator account plays a crucial role in the operation of the Thanos chain. It is mainly responsible for network upgrades, data availability, and network security.
Below is an explanation of the roles for each account:
Admin: the ability to upgrade contracts.Batcher: Publish Sequencer transaction data to L1.Proposer: Publish L2 transaction results (output roots) to L1.Sequencer: Sign blocks on the p2p network.Challenger: Resolve dispute game
Deployment Costs
Admin- 0.6 ETHThe admin fee constitutes the primary deployment expense, covering the deployment of system contracts on L1. This process requires approximately 80,000,000 gas. Assuming a base fee of 7–8 gwei, the estimated cost is approximately 0.6 ETH.
This cost is a one-time expense necessary to establish the foundational infrastructure.
Batcher, Proposer, ChallengerPost-deployment, Batcher, Proposer, and Challenger accounts incur ongoing operational costs. These expenses are highly variable, depending on the network's configuration and usage patterns.
Sequencer - Not required.
To ensure smooth operation, users must define an operational funding strategy, including determining the appropriate funding intervals for these accounts. It is recommended to use the provided spreadsheet to estimate operational costs based on the desired network configuration. By doing so, users can allocate sufficient ETH to these accounts to cover anticipated expenses, thereby maintaining seamless network functionality.
2. L1 RPC endpoint
You need an L1 RPC endpoint to handle deposits, withdrawals between L1 and L2 chains, and to ensure data availability and security for the L2 chain.
We currently recommend Alchemy as the L1 RPC endpoint provider. Since Thanos is an Ethereum-based L2 chain, make sure to select Ethereum.
3. Beacon RPC endpoint
To reduce data availability costs by using blobs. You’ll need to set up a Beacon node. You can create an endpoint through Quicknode.
4. Set-up AWS account
Terraform is used to set up an AWS-based infrastructure to deploy the Thanos chain. For Terraform to function properly, it needs to be integrated with your AWS account.
Create IAM user
In the IAM console, navigate to
Usersand clickCreate User.
Enter the User name and click the
Nextbutton.
To select the
Attach policies directlyoption and proceed with the deployment, you need most of the permissions for AWS resources, so selectAdministratorAccess.
Click the
Nextbutton, then click theCreate userbutton to create the user.On the user screen, click on the newly created user.
In the
Security credentialstab, clickCreate access key.
Select
Command Line Interfaceas the use case and clickNext.
Click on
Create access key.
Copy and store the
Access keyandSecret access key.
Configure the settings using the AWS command.
Use the following command to verify that the registration was successful.
Once the setup is complete, proceed to the next phase
5. Stake TON as an Operator
In the current Thanos Beta release, the operator registration mechanism for TON staking is not yet integrated.
This feature will be introduced in Staking v2.5, which is currently undergoing audit. However, operators who wish to explore staking early can use Staking v1 to stake TON and earn seigniorage rewards.
Note: TON staked in Staking v1 cannot be migrated to Staking v2.5 for operator registration.
6. Tools
To use the Thanos stack, you will need the following tools:
^2
^1.21
^20
^8
0.2.0
^3
^1.6
^2
^2.1
^1.9
^1.28
^3
Last updated
