Deploy New Rollup Chain

How to deploy a new Rollup chain?

Typical Deployment Time : 40~50 minutes

In this section, we’ll guide you through deploying a Thanos-based L2 chain with TON as the native token. The process involves four steps:

If you don’t have any aws access key, please refer this guide and create new one.

1. Network and chain configuration

2. Accounts and AWS setup

3. Staking/DAO candidate registration

4. Review configuration and deploy

Follow the instructions below to complete your chain deployment successfully:

In the Rollup tab, click on the Deploy New Rollup button in the top-right corner or select Create Rollup to begin the chain deployment process.

• Step 1 - Network and Chain Configuration

  1. The operator must first select the network type and provide a chain name. Currently, the platform supports only testnet deployments.

     
  2. In the L2 configuration step, the operator must enter the L1 RPC URL and L1 Beacon URL. If these terms are unfamiliar, simply follow the below steps to get it:

     Alchemy - L1 RPC URL

     DRPC - L1 Beacon URL (Not available now)

     L1 RPC URL, you will need it when during deployment. (You can get it from QuickNode, Alchemy, ChainList etc.) If you want to use L1 endpoint as a free plan, we recommend to use Alchemy. They provide API credits and RPS suitable for testing purpose.

     • Example : https://boldest-newest-patron.ethereum-sepolia.quiknode.pro/4ed7d53b815c434c082db3eb2f49612c914afe71/ from QuickNode

     Beacon URL (Get your endpoint from QuickNode by logging in, selecting Ethereum Sepolia, and opting for a free plan.)

     • Example: https://boldest-newest-patron.ethereum-sepolia.quiknode.pro/4ed7d53b815c434c082db3eb2f49612c914afe71/

     Note: While you can use a single QuickNode URL for both L1 RPC and the Beacon URL, it’s not recommended due to potential rate limiting issues. It’s better to use separate URLs for each. ℹ️ We recommend you to use Alchemy for L1 RPC and QuickNode for beacon url.

     Please usehttps://ethereum-sepolia-beacon-api.publicnode.com as L1 Beacon URL.

     

     If you’re comfortable with advanced settings, you can configure them by selecting the checkbox and following the guide to understand the relevance of each parameter. You may skip the advanced configurations and the platform will use default values during deployment.

     Once you entered all the information, click on “Next” at the bottom right corner.

• Step 2 - Account and AWS Configuration

  1. In this step, the user will be prompted to enter the seed phrase for the account holding the Ether balance (Testnet) needed to deploy the chain. If you want to know more about this, please see Step 4 in the prerequisite section. Once you provide the seed phrase, the you need to select the desired account(s) that will be used for chain deployment.

     - Admin Account
     - Proposer Account
     - Batch Account
     - Sequencer Account

     Note: These accounts will be assigned to different roles: admin, sequencer, batcher, and proposer. While you can use the same account for multiple roles, we recommend using separate accounts to avoid a single point of failure.

     Each account requires a minimum ETH balance. Please fund them accordingly based on the information below.

     • Admin account (minimum ${estimated_cost} ETH required) // It depends on the network status at the deployment time

     • Sequencer account (no need of ETH balance)

     • Batcher account (0.3 ETH recommended)

     • Proposer account (minimum 0.3 ETH recommended)

  2. If user does not provide that then there’s also a feature that the platform will create it for the user and then user could add balance in that. This could be done by clicking on Generate Random button. If you generate a random seed phrase using this method, make sure to fund the associated address with the required ETH balance. Please look at step 4 in this section to figure out the ETH balance.

     

     image.png
  3. The operator next need to select an AWS key for the deployment. Operator can add new or choose a saved one.

     

     image.png

     

     image.png
  4. Once the key is selected, please choose a region for the deployment

     

     image.png
  5. Click Next.

• Step 3 - Staking/ DAO Candidate Registration (This Step is optional and could be skipped)

  In this step, the operator provides the necessary information to register their chain with Staking v2, enabling them to receive seigniorage in the future.

  1. Enter the amount of TON you wish to stake. Ensure that the admin account selected in the previous step holds this balance. The minimum staking requirement is 1000.1 TON. You may request TON faucets in Sepolia from - https://sepolia.etherscan.io/address/0xd655762c601b9cac8f6644c4841e47e4734d0444#writeContract#F1 (If you generated an address using a random seed phrase and it doesn’t present in MetaMask, please contact the TRH team to request TON for testing).

     

     image.png
  2. Please provide a memo to appear in the staking v2 dashboard (mandatory)

  3. Please provide a name (optional)

  4. Click Next

• Step 4 - Review the details and deploy the chain

  Review the details you entered in the previous step. To make any changes, use the Previous button to go back. Once everything is verified, click the Deploy Rollup button

  

  image.png

How to verify the Deployment?

1. After clicking the Deploy Rollup button, you can monitor the chain deployment on the Rollup tab page.

   

   image.png
2. To view real-time deployment logs, click on the chain and check its deployment history.

   

   image.png
3. You can watch the real time logs

   

   image.png
4. Once the chain is successfully deployed, the deployment history will be shown like below.

1. You can also view integrations through the Integrations tab. By default, the bridge is installed with every chain deployment. If you provided details to register a candidate during deployment, the staking candidate integration will also be displayed, as shown in the screenshot below.