EXPLOREINDUSTRIESGUIDESLEARNGLOSSARYBOOKSWHITEPAPERTOOLSRESOURCESPIONEERMARKETSCOUNTRIESFEESMISSION FUNDPASSPORT
SUPPORTLOGINJOIN THE PROTOCOL →
GETREADYANDJUMP.COM · BUILT IN DETROIT

PROTOCOL NODES
ON GRAJ.

Protocol Nodes on the GRAJ protocol. One fee. 195 countries. Join the protocol.

JOIN THE PROTOCOL →
Protocol

RUNNING
A NODE.

Being built

A protocol that runs on infrastructure one company controls is a platform with better vocabulary. Nodes are the answer to that — independently operated instances that participate in the network — and they are designed rather than running, which this page says rather than implies.

Why it matters that it is not built yet

Decentralization claimed without operating nodes is the exact thing this protocol argues against. Naming the gap is more useful than a diagram implying a network that has one participant.

What a node would be responsible for

Holding a copy of the records it participates in, validating what it accepts, and remaining independently operable if the primary instance is unavailable. Anything less is a mirror rather than a node.

The hard part is not the software

It is agreeing what a node must validate and what happens when two disagree. Those rules have to be settled before anybody runs one, because changing them afterwards means changing every participant at once.

What exists today

An append-only event log with hash-linked entries, which is the substrate a node would replicate. The replication, validation and disagreement rules do not exist yet.

Where to go next
/append-only/protocol-fork/protocol/pillars
JOIN THE PROTOCOL