Network architecture & status

GRID currently runs as a public pilot: one Genesis authority produces signed blocks, independent peers verify and replicate them, the coordinator assigns useful work, and public APIs expose privacy-preserving telemetry.

Consensus boundary: block production is Genesis-led today. P2P verification is live, but permissionless block production and decentralized finality are not yet implemented.

Architecture overview

People + devices

Operators and wallets

Node operators use the CLI. ARK signs locally on iPhone, Mac, and Android without exposing private keys.

Native custody boundary

ARK wallets

Encrypted QR pairing, Keychain or Keystore custody, local signing, and nonce-based replay protection.

Caraveo/grid-wallets

Public edge

Website + secure API

Native downloads live at grid-compute.com. Signed envelopes enter through ark.grid-compute.com.

signed requests only

Useful work

Coordinator

Assigns authorized work and verifies results before producing settlement receipts.

Protocol core

GRID node + CLI

v0.2.24

Verifies ARK signatures, rejects replayed nonces, runs useful compute, maintains chain state, and speaks encrypted P2P.

Caraveo/grid

Independent replicas

P2P peers

Replicate blocks and independently verify signatures, links, state roots, and deterministic allocation.

verified settlements + replicated state

GENESIS

Current canonical authority

Signed settlement chain

The truth service, block producer, and bootstrap peer publish the canonical Phase 1 chain. Multi-validator finality remains a mainnet milestone.

Trust boundary: wallet secrets remain on the user's device. The network receives signed envelopes and independently verifies them before state changes are accepted.

Contributors should preserve these boundaries: wallets own custody and signing, the ARK edge accepts signed envelopes, GRID core owns validation and replay protection, and Genesis currently anchors canonical Phase 1 state. A service may relay data across a boundary; it must not silently absorb the responsibility on the other side.

Public topology

Component	Public address	Responsibility
Genesis truth	https://genesis.grid-compute.com	Signed network truth, health, chain snapshots
Genesis P2P	genesis.grid-compute.com:9900	Default bootstrap peer, gossip, block replication
Coordinator	https://coordinator.grid-compute.com	Job claims, verification, receipts, reward status
Explorer	https://explorer.grid-compute.com	Blocks, settlements, capacity, peers, health
Public mesh	https://grid-compute.com/api/mesh	Coarse node presence without public IP addresses

Work-to-block flow

text

miner / host
    │ claims authorized work
    ▼
coordinator ── verifies intent + result ──► settlement receipt
                                                  │
                                                  ▼
Genesis producer ── deterministic PoR allocation ──► signed block
                                                  │
                                                  ▼
P2P peers ── verify signature, chain link, state root, and allocation replay

Coordinator reward amounts are not blindly trusted by replicas. A block carries the inputs required to replay its allocation. Peers reject invalid signatures, broken previous-hash links, unverified settlements, malformed commitments, or allocation mismatches.

Trust anchors

The canonical Genesis hostname is compiled into the current CLI as the default P2P bootstrap and truth endpoint.
The current Genesis leader public key is a client trust anchor. Private signing and recovery keys are not published.
Genesis truth snapshots are signed and use a monotonic epoch so peers can reject stale policy.
Peer gossip can introduce additional peers; it cannot forge Genesis signatures or valid settlement blocks.

Join the P2P fabric

bash

# Initialize once
grid init --name garage --class S

# Genesis is dialed automatically
grid peer --name garage --with-bench

# Explicit extra peers may be added
grid peer --name garage --connect peer.example:9900

The default listener is 0.0.0.0:9900. Make that port reachable only if you intend to accept inbound peers. A node can still dial Genesis and participate behind ordinary outbound NAT.grid peer is the peer-only mode. Use grid node for the all-in-one process: encrypted P2P replication + host + mine.

Signed public presence

A location-enabled node creates a dedicated Ed25519 heartbeat identity with restrictive local permissions. Every pulse signs its timestamp, random nonce, coarse map coordinates, class, region, and status. The receiving Worker derives the public node id from the public key and uses one SQLite-backed Durable Object per node to reject replay atomically. Coordinates are rounded to 0.5° before public storage; IP addresses, ports, hostnames, wallets, and private keys are not stored.

bash

export GRID_GLOBE_LAT=39.5      # use a coarse nearby-city location
export GRID_GLOBE_LNG=-105.0
export GRID_GLOBE_REGION=NA-W
grid node

Decentralized mainnet gate

bash

grid mainnet
grid mainnet --json

# One-time blocks.json migration; legacy file is retained read-only
grid mainnet --migrate-storage

The gate is fail-closed. It remains red while Genesis is the only finalizing signer, fewer than four independent validators exist, quorum certificates are not enforced by block validation, treasury consensus state is absent, append-only block persistence is not active, or an external security review is outstanding. GRID has 3-of-4 validator-certificate verification primitives now; proposal, vote, finalization, leader-failover transport, and indexed storage remain the production milestone.

Local and custom networks

Development tools and Phoenix wallet settings may target a local or custom node. That is useful for testing, but it creates a different trust boundary. The public pilot defaults to the canonical Genesis endpoints above.

Read live status

bash

curl -fsS https://grid-compute.com/api/explorer \
  | jq '{checkedAt, health, chain: .chain | {chainId, height, tipHash}}'

curl -fsS https://grid-compute.com/api/mesh \
  | jq '{stats, genesis, peers}'