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.

Public topology

Work-to-block flow

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

# 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.

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

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 Ember 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

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}'