Tools

To use the Thanos stack, you will need the following tools:

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

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.

Deployment Costs

• Admin - 0.6 ETH
  • The 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, Challenger
  • Post-deployment, Batcher, Proposer, and Challenger accounts incur ongoing operational costs. These expenses are highly variable, depending on the network's configuration and usage patterns.
    • The explanation and process for customizing parameters can be found at: Chain Configuration
    • You can input the desired parameters to calculate the fees in the following spreadsheet: Thanos Stack Operation Fee Adjustment Spreadsheet
• Sequencer - Not required.

<aside> 💡

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.

</aside>

L1 RPC endpoint