Prerequisites
Beacon URL: (Get your endpoint from QuickNode by logging in, selecting Ethereum Sepolia, and opting for a free plan.)
Example: RPC by Quicknode
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.
Prepare AWS credentials & configuration to access AWS EKS.
Follow steps 1 to 9 in this guide to set up an IAM user with the required privileges and create an access key which will be later used with SDK.
What is IAM? (*Note: This IAM user has to have the following policies)
arn:aws:iam::aws:policy/aws-service-role/AmazonEKSServiceRolePolicy
Prepare a seed phrase for the L1 account. The SDK will prompt you to provide a 12-word seed phrase to generate EVM accounts for deployment. The simplest approach is to create a new MetaMask wallet with a 12-word seed phrase and fund at least the first four EVM accounts with Sepolia ETH.
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 timeSequencer account (no need of ETH balance)
Batcher account (0.3 ETH recommended)
Proposer account (minimum 0.3 ETH recommended)
Make sure you meet the above prerequisites before proceeding to the next step.
Last updated
