dKargo Docs
dKargo.ioWhitepaper
Docs ENG
Docs ENG
  • Welcome to dKargo
  • Run dKargo Node
    • Chain RPC
    • Installation Guide
    • Types of Chain Node
    • Full Node
    • Archive Full Node
    • Validator Node
  • Wallet Setup
    • Connectiong to MetaMask
    • Creating a wallet
    • Importing a Wallet
    • Adding the dKargo Network
  • Validator Operations
    • Validator Staking
    • Staking
    • Unstaking
    • Claim
  • Deploy Contract
    • How to deploy a contract
    • Deploying a Contract Using Remix-IDE
    • Deploying a Contract Using Hardhat
    • Deploying a Contract Using Foundry
  • ERC-20 BRIDGING
    • ERC-20 Bridging
    • Standard Gateway
    • Generic-custom Gateway
    • Custom Gateway
  • DKA Bridging
    • DKA Bridging
    • DKA Deposit
    • DKA Withdraw
  • Faucet
    • Faucet for Testnet Tokens
    • Claiming Testnet Tokens
  • Chain Snapshot
    • Download the Latest Chain Snapshot
  • Contract Address
    • Contract Address List
  • Bug Bounty
    • Bug Bounty Program
Powered by GitBook
On this page
  • L2 Arbitrum RPC EndPoints
  • Docker Images
  • L3 RPC EndPoints
  • ENV
  • Node Port
  • DIR
  1. Run dKargo Node

Installation Guide

PreviousChain RPCNextTypes of Chain Node

Last updated 1 month ago

L2 Arbitrum RPC EndPoints

URL information for communicating with Arbitrum, the base layer of dKargo’s L3.

To avoid rate limits, replace the Arbitrum One RPC URL with a private URL.

Docker Images

Docker image paths for running a dKargo node.

L3 RPC EndPoints

Relayer node information for receiving data from dKargo Chain or sending transactions.

  • https endpoint: https://warehouse-relayer.dkargo.io

  • wss endpoint: wss://warehouse-relayer.dkargo.io

ENV

Environmental variables required for node execution.

Node Port

  • 8547: http

  • 8548: websocket

DIR

"LOCAL_DATA_PATH": Local directory for storing full node data.

When setting up a node, manual configuration is required based on the user’s environment.