Archive Full Node

An Archive Full Node retains all functionalities of a Full Node while preserving the entire historical record of the blockchain without deletion. Additionally, it supports debugging interface calls.

Due to these characteristics, an Archive Full Node is ideal for in-depth data analysis and debugging operations.

1. Mainnet

1-1. Public L2 Arbitrum RPC EndPoints

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

• https://arb1.arbitrum.io/rpc

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

1-2. Docker Images

• Latest Docker Image: repo.dkargo.io:59083/mainnet-archivenode:v0.0.1

1-3. L3 RPC EndPoints

• https endpoint: https://mainnet-rpc.dkargo.io

• wss endpoint: wss://mainnet-ws.dkargo.io

1-4. Required Custom Options

• --init.url

  • Snapshot URL for downloading initialization data to enable fast synchronization.

• --parent-chain.connection.url

  • Base layer endpoint URL (Default: Arbitrum public RPC endpoints).

• --node.data-availability.parent-chain-node-url

  • Base layer endpoint URL (Default: Arbitrum public RPC endpoints).

1-5. Running a Node via Docker

docker run -d -p 8547:8547 -p 8548:8548 -v "<LOCAL_DATA_PATH>:/home/user/.arbitrum" repo.dkargo.io:59083/mainnet-archivenode:v0.0.1

LOCAL_DATA_PATH: The local PC path where the node data is stored.

1-6. Snapshot Sync

docker run -d -p 8547:8547 -p 8548:8548 -v "<LOCAL_DATA_PATH>:/home/user/.arbitrum" repo.dkargo.io:59083/mainnet-archivenode:v0.0.1 --init.url=<SNAPSHOT_URL>

SNAPSHOT_URL: The URL where the snapshot data is provided. For more details, please refer to Chain Snapshot.

1-7. Example(with snapshot)

docker run -d -p 8547:8547 -p 8548:8548 -v "<LOCAL_DATA_PATH>:/home/user/.arbitrum" repo.dkargo.io:59083/mainnet-archivenode:v0.0.1 --init.url="https://dkargo-snapshot.s3.ap-northeast-2.amazonaws.com/prune/latest/pruned.tar.gz"

2. Warehouse (Testnet)

Warehouse is a testnet that allows users to experiment before the official launch of the dKargo Mainnet.

2-1. Public L2 Arbitrum RPC EndPoints

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

• https://sepolia-rollup.arbitrum.io/rpc

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

2-2. Docker Images

• Latest Docker Image: repo.dkargo.io:59083/warehouse-archive:v0.0.1

2-3. L3 RPC EndPoints

• https endpoint: https://rpc.warehouse.dkargo.io

• wss endpoint: wss://ws.warehouse.dkargo.io

2-4. Required Custom Options

• --init.url

  • Snapshot URL for downloading initialization data to enable fast synchronization.

• --parent-chain.connection.url

  • Base layer endpoint URL(default: Arbitrum public RPC endpoints)

• --node.data-availability.parent-chain-node-url

  • Base layer endpoint URL (Default: Arbitrum public RPC endpoints).

2-5. Running a Node via Docker

docker run -d -p 8547:8547 -p 8548:8548 -v "<LOCAL_DATA_PATH>:/home/user/.arbitrum" repo.dkargo.io:59083/warehouse-archive:v0.0.1

LOCAL_DATA_PATH: The local PC path where the node data is stored.

2-6. Snapshot Sync

docker run -d -p 8547:8547 -p 8548:8548 -v "<LOCAL_DATA_PATH>:/home/user/.arbitrum" repo.dkargo.io:59083/warehouse-archive:v0.0.1 --init.url=<SNAPSHOT_URL>

SNAPSHOT_URL: The URL where the snapshot data is provided. For more details, please refer to Chain Snapshot.

2-7. Example(with snapshot)

docker run -d -p 8547:8547 -p 8548:8548 -v "<LOCAL_DATA_PATH>:/home/user/.arbitrum" repo.dkargo.io:59083/warehouse-archive:v0.0.1 --init.url="https://warehouse-snapshot.s3.ap-northeast-2.amazonaws.com/archive/latest/archive.tar.gz"