▪️Deploy a Taiko Node using VPS AI

To get started with our VPS AI, you'll need to connect your preferred non-custodial EMV compatible Wallet. This procedure is simple and straightforward.

▪️Connecting Your Wallet to the VPS AI Dashboard

Once You've Successfully Connected Your Wallet, If Needed, Add Credit.

▪️Adding Credit to Your VPS AI Dashboard

Select "Deploy" from the Virtual Machine menu.

Configuring Your VPS Adding a VPS Name

When setting up your Virtual Private Server VPS, it's important to give it a unique, recognizable name. This allows for easier identification and management, especially when you're dealing with multiple servers. So take a moment to think of a suitable name for your VPS. In this case, we will go with "taiko-node"

Recommended VPS Configuration for Running a Taiko Node

To configure your Virtual Private Server (VPS) for optimal performance, you need to select the appropriate computing specifications. We recommend the following configuration for running a Taiko node: 16 GiB of memory, 4 vCPUs for processing power, and 2TB of storage space. However, if 2TB is not feasible for you, make sure you have a minimum of 1TB storage to ensure smooth operation of the Taiko node.

Data Center Selection

You have the option to select a specific Data Center for your operations, or if you would prefer, you can leave this field blank. By doing so, our system will automatically make a selection for you. This system is designed to analyze various factors and conditions to ensure the optimal choice of Data Center for your specific needs and requirements.

Choosing the right Operating System

For this setup, it is essential to select Ubuntu 22 as the operating system.

Adding SSH Key & Root Password

The first step in setting up your Virtual Private Server VPS involves authentication through an SSH Key. This is a vital step in ensuring the security of your server. If you already possess an SSH Key, simply select it from the available list. If you do not have an SSH Key, you can create a new one. Follow the provided instructions to create and add your new SSH Key.

Once you have successfully provided an SSH Key, the next step is to add your root password. This password is a critical element for securing your server, preventing any unauthorized access. It is advised to choose a strong password, incorporating a mix of letters, numbers, and special characters, to enhance your server's security.

Remember to keep your root password confidential to avoid potential security risks.

Choosing a Duration of Your VPS

Opt for the duration of your VPS (for instance, 1 week). The system is designed to automatically renew as long as you have sufficient credit in your account. Please note, this is a fully decentralized system, so there's no need for credit card attachments, it operates purely on a credit-based system.

Confirmation & Deploying your VPS

First, you'll want to locate and click on the "Confirm & Deploy" button. Once you've done this, take a moment to thoroughly review the provided specifications. Make sure you understand all aspects of the deployment process. After you've completed your review and feel confident in your understanding, proceed by confirming the deployment.

Waiting the Machine & Copy SSH Command

After initiating your machine, please allow some time for it to fully boot up. There may be occasions where this process isn't instantaneous, and a delay might occur. If this happens, don't worry, just refresh your page. Once your machine is up and running, locate and click on the 'Copy SSH Command' button.

After your machine is fully booted and running, copy the Secure Shell (SSH) command provided in the previous steps. This command will allow you to initiate a secure connection to your machine. Paste the copied SSH command into your terminal or command prompt and press enter to execute it. This will initiate the SSH session, allowing you to securely connect to your machine.

Preparing The Machine

To prepare your machine for running a Taiko Node using VPS AI, you need to install Docker. Here is a comprehensive guide to help you through the process:

Updating Existing Packages: Before you begin installing Docker, it's important to ensure that all existing packages are up-to-date. Execute the following command in the terminal:

sudo apt update

Installing Prerequisite Packages: Docker requires certain packages to function correctly. These packages allow apt to use packages over HTTPS. Install these by running:

sudo apt install apt-transport-https ca-certificates curl sof
tware-properties-common

Adding Docker's Official GPG Key: Docker has an official GPG (GNU Privacy Guard) key that is required by your system. This key is used to sign all data that is sent to and received from Docker, ensuring its authenticity and integrity. Add this key to your system using the following command:

curl -fsSL <https://download.docker.com/linux/ubuntu/gpg> | s
udo apt-key add -

Adding Docker Repository to APT Sources: APT (Advanced Package Tool) is a package management system used by Ubuntu. To install Docker, you need to add its repository to the APT sources. Run the following command to accomplish this:

sudo add-apt-repository "deb [arch=amd64] <https://download.d
ocker.com/linux/ubuntu> $(lsb_release -cs) stable"

Updating Package Database: After adding the Docker repository to the APT sources, you need to update the package database. This will allow your system to access the Docker packages from the newly added repository. Update the package database using:

sudo apt update

Verifying Docker Installation Source: Before installing Docker, it's essential to verify that you're installing from the Docker repository and not the default Ubuntu repository. Run the command below to confirm this:

apt-cache policy docker-ce

Installing Docker: You are now ready to install Docker. Use the following command to start the installation process:

sudo apt install docker-ce

Checking Docker Installation: After installing Docker, you should check if it is installed and running properly. Execute the following command to check Docker's status:

sudo systemctl status docker

By following these steps, you should now have Docker installed and running on your system, ready for deploying a Taiko Node on your VPS AI.

Deploying Taiko Node

After you finished installing docker, lets follow the Taiko Official Guide here:

https://docs.taiko.xyz/guides/node-operators/run-a-taiko-node-with-docker/

1. Clone simple-taiko-node

• Mac/Linux

• Windows Terminal Window

git clone <https://github.com/taikoxyz/simple-taiko-node.gitcd> simple-taiko-node

2. Copy the Sample .env Files Info

   To run a hekla Taiko node please copy .env.sample.hekla instead of .env.sample. Terminal Window

cp .env.sample .env

3. Set the L1 Node Endpoint First, open the .env in your preferred text editor: - Mac/Linux - Windows Terminal window nano .env

Note

You can use any L1 endpoint to run a Taiko L1 node unless you want to prove blocks past the last 128 blocks, in which case you will need an archive node. Itʼs recommended to run a local L1 node but you browse around for other RPC Providers. Keep in mind they will eventually rate limit your node and it will stop syncing, so a local L1 node is recommended for a proper setup.

For Mainnet, the L1 Node will need to be an Ethereum node; for Testnet, the L1 Node will need to be a Etherem testnet (Holesky) node.

4. Next, you will set the L1 node endpoints. If you are running a local L1 node, you cannot reference the L1 endpoints as http://127.0.0.1:8545 , ws://127.0.0.1:8546 and http://127.0.0.1:5052 because that is local to inside the simple-taiko-node Docker networking. Instead you can try:

• Using host.docker.internal (see: stack overflow).

• Using the private ip address of your machine (use something like ip addr show to get this ip address).

After getting the address of the L1 node, set the following L1 node endpoints in

your .env file. Here is an example: L1_ENDPOINT_HTTP=http://192.168.1.15:8545 - -L1_ENDPOINT_WS=ws://192.168.1.15:8546 L1_BEACON_HTTP=http://192.168.1.15:5052

4. Remove Old Testnet Volumes If you ran a testnet node previously, make sure to first remove the old volumes:

   Terminal Window

       docker compose down -v

5. Set the Profiles You Want to Run

   In your .env , please set COMPOSE_PROFILES to whichever set of services youʼd like to run in a comma separated list (i.e., l2_execution_engine,proposer,prover or any combination of the three).

Note that if you include proposer or prover , the services will still be disabled if you do not set ENABLE_PROPOSER=true or ENABLE_PROVER=true respectively.

6. Start the node

   Info

   Make sure Docker is running and then run the following command to start the node

you may need to use sudo docker compose up -d if your user is not in the docker group

To run a hekla Taiko node please use the following command instead: docker-compose-hekla.yml up -d .

Terminal Window

    docker compose up -d

7. Verify Node is Running

Option 1: Check with the Node Dashboard

A node dashboard will be running on localhost on the GRAFANA_PORT you set in your .env file, which defaults to 3001 : http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview.

You can verify that your node is syncing by checking that the chain head on the dashboard is increasing. Once the chain head matches whatʼs on the block explorer, you are fully synced.

Option 2: Check with Curl Commands

1. Check if the Execution Layer client is connected to Taiko L2:

Terminal Window

curl <http://localhost:8547> \\  -X POST \\  -H "Content-Type: application/json" \\

Which should return the chainId as 0x28c61 (167009):

{ "jsonrpc": "2.0", "id": 1, "result": "0x28c61" }

2. Check if the Execution Layer client is synced by requesting the latest Taiko L2 / L3 block from the Execution Layer client:

Terminal Window

If the blockNumber response value is 0 or not growing, check the Taiko L2 logs here:

// Some codecurl <http://localhost:8547> \\  -X POST \\  -H "Content-Type: application/json" \\
 

Terminal Window

    docker compose logs -f

You may need to use sudo docker compose logs -f if you are not in the docker group.

For Additional Help, Please Visit Our Contact & Help Page Below.

🟩Contact & Help