🔹Running a Node

Running your own Orbion node provides full access to network data without relying on public RPC endpoints. It allows greater flexibility, performance, and independence — especially for indexers, explorers, validator operators, and backend teams.

This guide outlines the steps to launch a standard full node on the Orbion Testnet.

---

🧾 Requirements

Resource	Minimum	Recommended
CPU	2 cores	4+ cores
RAM	4 GB	8–16 GB
Storage	100 GB SSD	250+ GB NVMe
OS	Ubuntu 20.04+	Any Linux/macOS
Bandwidth	10 Mbps	50+ Mbps

---

⚙️ Step 1: Install the Node Binary

⚠️ Coming soon: official release binaries will be hosted at orbionchain.com/releases

For now, build from source (if repo is public), or install from precompiled binaries once available:

wget https://orbionchain.com/releases/orbiond
chmod +x orbiond
sudo mv orbiond /usr/local/bin/

---

🧭 Step 2: Initialize the Chain

orbiond init "MyNode" --chain-id orbion-testnet

This will generate the config directory and initial node identity.

---

🧬 Step 3: Download Genesis File

wget https://orbionchain.com/genesis.json -O ~/.orbiond/config/genesis.json

Ensure the file matches the expected hash from the documentation or community channels.

---

🌐 Step 4: Configure Peers & RPC

Edit ~/.orbiond/config/config.toml:

# Minimum peers to connect
seeds = "seed1@ip1:26656,seed2@ip2:26656"

# Optional: make node public
laddr = "tcp://0.0.0.0:26657"

# Enable RPC
rpc:
  cors_allowed_origins = ["*"]
  max_open_connections = 100

---

🚀 Step 5: Start the Node

orbiond start

To run in the background:

nohup orbiond start > node.log 2>&1 &

Check sync status:

orbiond status | jq .sync_info

---

📡 Enable API for External Access (optional)

In ~/.orbiond/config/app.toml:

[api]
enable = true
swagger = true
address = "0.0.0.0:1317"

---

🧠 Archive Mode (for indexers)

To store full state history:

• Set pruning to nothing

• Enable index-all keys

In app.toml:

[pruning]
strategy = "nothing"

In config.toml:

tx_index = "kv"
index_all_keys = true

Warning: Archive nodes require large storage over time. Only use this if you're building explorers, analytics tools, or bridges.

---

🔐 Security Recommendations

• Protect port 26656, 26657, and 1317 with a firewall

• Use ufw or iptables to restrict access

• Keep binaries updated and verify checksums

• Backup your node keys (priv_validator_key.json, node_key.json)

---

Running your own node gives you full control over RPC access, faster indexing, and the ability to validate blocks and transactions in real time — without rate limits.