OriginTrail
  • Get started with OriginTrail
  • OriginTrail Ecosystem — Call for Papers (Coming Soon)
  • Key Concepts
    • Decentralized Knowledge Graph (DKG)
    • DKG key concepts
  • Build with DKG
    • Quickstart (test drive the DKG in 5 mins)
      • Quickstart with Node.js
      • Quickstart with Python
    • ChatDKG builder toolkit
      • DKG SDK
        • Development environment setup
        • DKG Javascript SDK (dkg.js)
          • Interact with DKG paranets
          • Knowledge submission & curation
          • Paranet's incentives pool implementation
        • DKG Python SDK (dkg.py)
      • DKG paranets
        • Deploying a DKG paranet
        • Building with DKG paranets
        • Syncing a DKG Paranet
        • Initial Paranet Offerings (IPOs)
          • IPO specification
          • Launching your IPO
          • Paranet's incentives pool
          • IPO voting
      • AI agents
        • ElizaOS DKG agent
        • Custom DKG Python agent
        • Custom DKG JavaScript agent
    • DKG Edge Node
      • DKG Edge Node architecture
      • Get started with the Edge Node boilerplate
        • Automated setup with the installer
        • Manual setup
        • Usage example
      • Customize & build with the Edge Node
      • Knowledge Mining and dRAG examples
      • Deploy your Edge Node based project
        • Automated deployment with installer
      • DKG Edge Node inception program
      • DKG Edge Node API documentation
    • DKG Core Node
      • Run a V8 Core Node on testnet
        • Preparation for V8 DKG Core Node deployment
        • V8 DKG Core Node installation
      • Run a V8 Core Node on mainnet
        • Preparation for V8 DKG Core Node deployment
        • V8 DKG Core Node installation
  • Delegated staking
    • Delegated staking—Introduction
      • Step-by-step staking
      • Redelegating stake
  • Integrated Blockchains
    • Base blockchain
      • Connect to Base
    • Gnosis chain
      • Connect to Gnosis
    • NeuroWeb
    • Teleport instructions - NeuroWeb
    • Bridging to Moonbeam
    • Deployed smart contracts
  • Bounties & rewards
    • General bug bounty
    • Code contributions & V8 bug bounty
  • Whitepapers & RFCs
    • OriginTrail whitepaper
    • OriginTrail RFCs
  • Useful Resources
    • What's new with OriginTrail V8
    • DKG V8 guidebook
      • Protocol updates
      • Feature roadmap
      • How to upgrade to V8?
    • Public nodes
    • Tutorials
    • Test token faucet
    • Development principles
    • Community created resources
    • Linked data & knowledge graphs
    • Available networks, network details and RPCs
    • OT Node Engine implementation details
      • Modules
      • Command Executor
    • Contribution guidelines
      • Guidelines for automated test contributions
    • Explore the OriginTrail ecosystem
Powered by GitBook
On this page
  • Mainnet node setup instructions (Base)
  • 1. Obtain Base Archival RPC Endpoint
  • 2. Acquire TRAC and ETH tokens
  • 3. Update DKG node configuration
  • 4. Restart your node
  • Testnet node setup instructions (Base Sepolia)
  • 1. Obtain Base Sepolia Archival RPC Endpoint
  • 2. Acquire TRAC and Sepolia ETH test tokens
  • 3. Update DKG node configuration
  • 4. Restart your node
  • Node Stake and ask setup:

Was this helpful?

Edit on GitHub
  1. Integrated Blockchains
  2. Base blockchain

Connect to Base

PreviousBase blockchainNextGnosis chain

Last updated 10 months ago

Was this helpful?

Since 6.5.0 release, OriginTrail DKG nodes support Base blockchain (Mainnet). Learn more about how to use your node with Base below.

Mainnet node setup instructions (Base)

Since the 6.5.0 release, your OriginTrail DKG node can operate on Base network. In order to connect your node to Base, please refer to the instructions below.

1. Obtain Base Archival RPC Endpoint

Refer to the or search for the RPC providers that offer Base RPC's.

Selecting an archival endpoint is a crucial requirement for the optimal functionality of your DKG node.

2. Acquire TRAC and ETH tokens

List of available exchanges is available on our .

Instructions on how to bridge TRAC and ETH tokens to Base blockchains can be found .

3. Update DKG node configuration

Open the .origintrail_noderc configuration file of your DKG node located inside the ot-node directory. Within the config, locate the "blockchain" object, and add the following object to the "implementation" array, specifying your RPC endpoint and wallets.

As operationalWallets is an array, you can define multiple operational wallets.

"base:8453": {
  "enabled": true,
  "config": {
    "sharesTokenSymbol": "shares_token_symbol",
    "sharesTokenName": "shares_token_name",
    "operatorFee": <value_between_0_and_100>,
    "rpcEndpoints": [
      "<Your Base RPC endpoint>/"
    ],
    "operationalWallets": [
      {
        "evmAddress": "0x0bf...",
        "privateKey": "0x1e3..."
      }
    ],
    "evmManagementWalletPublicKey": "0xd09..."
   }
 }

After adding "base:8453", your "blockchain" object in the configuration file should look like the one below:

...
    "blockchain": {
      "defaultImplementation": "otp:2043",
      "implementation": {
        "otp:20430": {
          "enabled": true,
          "config": {
            "sharesTokenSymbol": "shares_token_symbol",
            "sharesTokenName": "shares_token_name",
            "operatorFee": <value_between_0_and_100>,
            "operationalWallets": [
              {
                "evmAddress": "0x0bf...",
                "privateKey": "0x1e3..."
              }
            ],
            "evmManagementWalletPublicKey": "0xd09..."
          }
        },
        "gnosis:100": {
          "enabled": true,
          "config": {
            "sharesTokenSymbol": "shares_token_symbol",
            "sharesTokenName": "shares_token_name",
            "operatorFee": <value_between_0_and_100>,
            "rpcEndpoints": [
              "https://archive-rpc.chiado.gnosischain.com/"
            ],
            "operationalWallets": [
              {
                "evmAddress": "0x0bf...",
                "privateKey": "0x1e3..."
              }
            ],
            "evmManagementWalletPublicKey": "0xd09..."
           }
         },
         "base:8453": {
           "enabled": true,
           "config": {
           "sharesTokenSymbol": "shares_token_symbol",
           "sharesTokenName": "shares_token_name",
           "operatorFee": <value_between_0_and_100>,
           "rpcEndpoints": [
              "<Your Base RPC endpoint>"
           ],
           "operationalWallets": [
            {
              "evmAddress": "0x0bf...",
              "privateKey": "0x1e3..."
            }
          ],
          "evmManagementWalletPublicKey": "0xd09..."
         }
       }
      }
    },
...

4. Restart your node

You can proceed and restart your node to confirm that it will start communicating with Base.

Once again, make sure that your operational wallet has some Base ETH in order for your OriginTrail DKG node to be able to create the profile on the new network.

otnode-restart && otnode-logs

If you added everything successfully, your node will show the log that says “blockchain module initialized with implementation: base:8453”.

If you have come this far and your node logs are not showing any errors, you're node is successfully set up!

Testnet node setup instructions (Base Sepolia)

Since the 6.5.0 release, your OriginTrail DKG node can operate on Base Sepolia network. In order to connect your node to Base Sepolia, please refer to the instructions below.

1. Obtain Base Sepolia Archival RPC Endpoint

Selecting an archival endpoint is a crucial requirement for the optimal functionality of your DKG node.

2. Acquire TRAC and Sepolia ETH test tokens

TRAC faucet will be enabled soon via Discord bot, same as for the other networks and the usage instructions will be provided here.

3. Update DKG node configuration

Open the .origintrail_noderc configuration file of your DKG node located inside the ot-node directory. Within the config, locate the "blockchain" object, and add the following object to the "implementation" array, specifying your RPC endpoint and wallets.

As operationalWallets is an array, you can define multiple operational wallets.

"base:84532": {
  "enabled": true,
  "config": {
    "sharesTokenSymbol": "shares_token_symbol",
    "sharesTokenName": "shares_token_name",
    "operatorFee": <value between 0 and 100>,
    "rpcEndpoints": [
      "<Your Base Sepolia RPC endpoint>/"
    ],
    "operationalWallets": [
      {
        "evmAddress": "0x0bf...",
        "privateKey": "0x1e3..."
      }
    ],
    "evmManagementWalletPublicKey": "0xd09..."
   }
 }

After adding "base:84532", your "blockchain" object in the configuration file should look like the one below:

...
    "blockchain": {
      "defaultImplementation": "otp:20430",
      "implementation": {
        "otp:20430": {
          "enabled": true,
          "config": {
            "sharesTokenSymbol": "shares_token_symbol",
            "sharesTokenName": "shares_token_name",
            "operatorFee": 5,
            "operationalWallets": [
              {
                "evmAddress": "0x0bf...",
                "privateKey": "0x1e3..."
              }
            ],
            "evmManagementWalletPublicKey": "0xd09..."
          }
        },
        "gnosis:10200": {
          "enabled": true,
          "config": {
            "sharesTokenSymbol": "shares_token_symbol",
            "sharesTokenName": "shares_token_name",
            "operatorFee": 5,
            "rpcEndpoints": [
              "https://archive-rpc.chiado.gnosischain.com/"
            ],
            "operationalWallets": [
              {
                "evmAddress": "0x0bf...",
                "privateKey": "0x1e3..."
              }
            ],
            "evmManagementWalletPublicKey": "0xd09..."
           }
         },
         "base:84532": {
           "enabled": true,
           "config": {
           "sharesTokenSymbol": "shares_token_symbol",
           "sharesTokenName": "shares_token_name",
           "operatorFee": <value_between_0_and_100>,
           "rpcEndpoints": [
              "<Your Base Sepolia RPC endpoint>"
           ],
           "operationalWallets": [
            {
              "evmAddress": "0x0bf...",
              "privateKey": "0x1e3..."
            }
          ],
          "evmManagementWalletPublicKey": "0xd09..."
         }
       }
      }
    },
...

4. Restart your node

You can proceed and restart your node to confirm that it will start communicating with Base Sepolia.

Once again, make sure that your operational wallet has some Base Sepolia ETH in order for your OriginTrail DKG node to be able to create the profile on the new network.

otnode-restart && otnode-logs

If you added everything successfully, your node will show the log that says “blockchain module initialized with implementation: base:84532”.

If you have come this far and your node logs are not showing any errors, you're node is successfully set up!

Node Stake and ask setup:

Refer to the or search for the RPC providers that offer Base RPC's.

Please refer to to see the list of available faucet providers. In order to obtain TRAC tokens on Base Sepolia, please contact tech@origin-trail.com.

If you are running a node, setting up stake and ask is not required.

Please refer to "" part of our documentation for more details regarding setting up stake and ask parameters.

official Base documentation
website
here
official Base documentation
Base official documentation
Gateway
Running a full node
Page cover image