GOD ChainBY ETKINGDOMBack to GOD Chain
PARTICIPATION · OPERATOR GUIDE
Synthetic testnet · Technical preview

Run a node.Keep your keys.
Understand your role.

A node runs on your computer or server, verifies blocks and follows GOD Chain. An eligible validator also participates in consensus. Opening a wallet, a browser tab or an extension does not run a node.

THREE DIFFERENT WAYS TO PARTICIPATE

Choose your role.

WALLET PARTICIPATION

Delegate GOD

Delegate through a supported wallet to a validator. You do not run a node or hold its consensus key.

  • No node process on your device.
  • Delegated funds are not immediately spendable.
  • Rewards depend on protocol eligibility and verified contributions, not a promised return.
NON-SIGNING REPLICATION

Observer node

Run a separate process to replay retained blocks and follow new committed state. It never votes or proposes blocks.

  • No stake required for the observer role.
  • No validator G reward for replication alone.
  • Cannot become a validator by editing its role or resetting signing state.
CONSENSUS PARTICIPATION

Validator candidate

Keep your own node keys, synchronize, register with self-stake and meet the network's selection rules.

  • Registration alone does not make you an active validator.
  • Sign only when committed state admits your key to the signing set for that height.
  • Eligible, verified signatures can earn G; uptime alone is not a reward guarantee.

Independent operation means participants control their own machines and signing keys. Node counts, peer counts and location labels do not prove independent control. The current pilot is not an independently operated, geographically distributed network.

WHAT YOU CAN RELY ON TODAY

Current availability.

Node software
Command-line program: godd. No graphical node dashboard or one-click node installer has been released.
Linux and macOS
Private developer-run startup and recovery checks exist. This is not blanket certification of every computer, host or network layout.
Windows
Private node disk operations remain disabled pending owner-only permission support and verification. Cross-compilation is not runtime acceptance.
Self-service joining
Observer joining and a separate validator-candidate workflow have passed isolated tests. The new candidate path is not publicly activated on the existing pilot.
Downloads and network access
No public node binary, ready-to-use join bundle or open peer discovery service is supplied by this page. Do not use random configuration or an unofficial installer.
Minimum hardware
Not finalized. CPU, memory, SSD growth, bandwidth and uptime must be measured on ordinary computers before minimum specifications are published.

A public Chain ID or wallet RPC URL is not a node join configuration. Nodes also need the exact genesis, runtime policy, reviewed bundle digest and reachable P2P peers.

TECHNICAL WORKFLOW · NOT A PUBLIC ACTIVATION

How setup works.

  1. Obtain reviewed software

    Technical operators currently build from a reviewed source revision using the pinned toolchain and checksum-bound lifecycle build. Use the technical guide for the exact version. Do not bypass the required build patch or assume the latest source matches the deployed pilot.

  2. Verify the network configuration

    Obtain the exact synthetic bundle and compare its full digest through an independently trusted channel. Inspect the genesis, runtime rules, fees and peers. A checksum from the same untrusted download is not authentication.

  3. Create your local identity

    Initialize a fresh owner-only node directory with your own consensus and P2P keys. Keep a validator's wallet separately. Never send private keys to ETKINGDOM, a coordinator or a website, and never overwrite an existing node to join.

  4. Check connectivity, then synchronize

    Review P2P reachability, NAT and firewall rules on the intended host. Keep validator RPC on loopback. After checks and explicit startup, the node replays available blocks and follows the chain; verify committed progress against a trusted reference. A running process is not proof of synchronization.

  5. Register only if you intend to validate

    Use the separate candidate registration and offline wallet review path on a compatible proof-enabled synthetic network. Confirm self-stake, fees, owner and consensus key. The public read-only RPC and six-action wallet gateway do not accept validator registration. Observe successful committed registration and actual signing-set admission before expecting consensus participation.

Command-line examples for prepared test environments

These examples require a compatible reviewed binary and an already prepared private workspace. Every variable is operator-supplied; this page supplies no bundle, endpoint or staking address. Joining and registration must follow the guide for the exact network version.

./build/godd testnet inspect-bundle \
  --bundle "$GOD_BUNDLE_FILE" \
  --expected-bundle "$GOD_REVIEWED_BUNDLE_SHA256"

# Check only while this node is stopped.
./build/godd testnet check --home "$GOD_NODE_DIR"

# Start only after host, peer and configuration review.
./build/godd testnet start --home "$GOD_NODE_DIR" --allow-network

--allow-network permits the explicitly reviewed network listeners and peers. It does not authorize validation, enable real assets, open arbitrary RPC methods or activate the RH bridge.

Read the technical guide (opens in a new tab)Review the source (opens in a new tab)

The public snapshot can lag local development. Check the reviewed revision and its supported commands; this page is not a release manifest or permission to migrate an existing pilot.

YOUR IDENTITY · YOUR RESPONSIBILITY

Operate safely.

BEFORE YOU GET STARTED

Common questions.

Can I run a node by opening the wallet?

No. Wallet delegation and node operation are separate. A node is a persistent process on your computer or server, not a browser mining session.

Must I rent a server?

Not necessarily. A computer may be suitable after its resources, storage, connectivity and uptime have been tested. No ordinary-computer minimum is certified yet. Validators need reliable ongoing operation; an observer can stop and catch up later within the network's available block retention.

Does everyone who starts a node receive G?

No. Observers do not receive validator rewards. A candidate must register, meet selection rules and contribute eligible verified consensus signatures. Missed signatures do not earn the corresponding allocation. Reward settlement and liquidity are separate.

Can earned G always be exchanged for GOD?

No guaranteed rate or liquidity is promised. Redemption uses the settled pool and burns the offered G only when GOD payment succeeds. An empty pool does not erase G or prevent its other supported uses.

What still needs to be released for ordinary participants?

Reviewed platform packages, authenticated configuration delivery, secured public peering, cross-host joining and recovery checks, ordinary-computer measurements, and clear status/support tooling. Candidate registration and its funding/submission path also need public acceptance. Mainnet and bridge activation require separate review.

What can I safely include in a support request?

Your software version, operating system, action and redacted error category. Review screenshots first. Never send a wallet backup, passphrase, private key, raw configuration, unredacted logs or private faith text.