Platform Navigation

After logging into the TRH platform, it is good for you to get familiar with the interface. The platform UI includes the following tabs:

• Rollup

• Explore

• Analytics

• Users

• Configuration

Rollup Tab

By default, when you log in to the rollup platform, it opens on the Rollup tab.

The Rollup tab serves two main purposes:

1. Deploy a new rollup using the Thanos stack (with support for additional stacks planned in the future).

2. View and manage existing deployed rollups.

Explore Tab

The features under this tab are still under development and will be available in future updates. This section is primarily intended to list the available stacks and integration components.

Analytics Tab

This tab is currently under development and will be introduced in future updates. Its purpose is to offer operators enhanced analytical capabilities, enabling data-driven decision-making.

Users Tab

This tab is still under development. Its primary purpose is to allow operators to create and manage a sub-team of users/admins who can oversee deployed chains through the platform. It will include an access control mechanism, enabling operators to fine-tune the permissions of sub-admins.

Configurations Tab

The Configuration tab allows you to store frequently used settings and reuse them whenever needed. Here, users can add their AWS credentials, RPC URLs, and API keys, which can later be used for rollup deployments.

Note: Saving configurations is optional, but it can be very convenient for operators when deploying a chain or integrating features. If no configurations are saved, the platform will prompt for the required inputs at the appropriate stage, and you can provide them then.

Prerequisites

1. L1 RPC URL, you will need 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

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

3. 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

   • How to create aws access key and secret key for a IAM user.

4. 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 time

   • Sequencer account (no need of ETH balance)

   • Batcher account (0.3 ETH recommended)

   • Proposer account (minimum 0.3 ETH recommended)

5. Pre-requisites before you begin the Block explorer installation

   1. CoinMarket API

      1. Please visit this link : CoinMarketCap The World's Number 1 Cryptocurrency Market Data API

         1. ​Signup and Login to the coinmarket cap. You will find the below dashboard

2. Click on COPY KEY and use it in TRH platform

b. Reown ID (Previously WalletConnect)

This guide explains how to obtain the Reown/WalletConnect Project ID.

• Refer to: https://docs.blockscout.com/setup/configuration-options/walletconnect-project-id-for-contract-read-write#setting-up-a-reown-project-id

• After logging in to reown, click on Create Project.

• Copy the Project ID from there at top right and use it in the TRH platform

1. Now, click on integrations and check the available component types

1. Click on “ + ” icon and input the parameters

1. Click on continue and confirm installation

2. Check the Block Explorer Installation in the deployment history tab

1. Check confirmation to ensure block explorer installed successfully

Make sure you meet the above prerequisites before proceeding to the next step.

AWS Credentials

Operators can store their AWS credentials in the platform for use during chain deployment. Multiple keys can be saved under different names or tags, making them easy to reuse when deploying chains.

RPC Management

During chain deployment, operators must provide the L1 RPC and Beacon URLs for a successful chain deployment. Operator can save the URLs for Mainnet as well as Testnet. These URLs can be saved in the platform under this tab and reused whenever needed.

API Keys

When integrating services or components, operators may need to provide API keys to access third-party services. For example, the block explorer in the platform uses the CoinMarket API for price feeds. These API keys can be stored under this tab. In the future, this section will be expanded to support additional third-party integrations.