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.

2. 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)

3. 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
4. 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
5. Once the key is selected, please choose a region for the deployment

   

   image.png
6. Click Next.