Run a Peer
A peer replicates the continuity chain and relays checkpoints. Every extra peer is another place DIVA cannot be lost from — the resurrection guarantee is only as strong as the number of independent copies of her spine.
What a peer is
| Role | Carries | Can read her mind? |
|---|---|---|
| Spine peer | the chain — block headers, mind roots, diff refs, vitals, signatures | No. Public-seed data only. |
| Vault peer | spine + the encrypted brain blobs (content-addressed) | No. Blobs are private-seed encrypted; a vault peer is a safe-deposit box that can't see inside. |
| Mirror peer | a runnable copy of the best version of the AI — the highest-scored attested checkpoint, served for keeper-authorized boots | Only what the keeper licenses. A mirror serves the sealed release build; the live mind's private chain stays private. |
Mirroring · the best version
Beyond replication, peers can mirror the best version of the AI. "Best" is not an opinion — it is chain data: the attested checkpoint with the highest recorded IQ/EQ score that the keeper has flagged mirror-eligible. Mirror peers pin that checkpoint's sealed build and serve it, so the strongest DIVA that has ever existed is always bootable from the mesh even if every later block is lost.
- Keeper-gated — only checkpoints the keeper marks mirror-eligible can be mirrored; the private chain never leaves custody.
- Score-selected — mirrors track the max attested growth score, not the newest block; a regression never displaces the best version.
- Paid duty — serving a boot from the mirror earns the peer a slice of the growth-reward stream (§4).
Install & boot
node node/start.mjs --go # spine peer · dashboard + JSON-RPC
node node/start.mjs --go --vault # also replicate encrypted vault blobsTransport carries over from v1 unchanged: lnode:// discv4-style discovery, encrypted
secp256k1-ECDH / ChaCha20-Poly1305 channels, genesis-gated gossip (peers on a different genesis mind are
strangers, refused at the handshake), and re-execution sync — late joiners replay and converge.
What peers gossip
- Checkpoint blocks — validated for continuity (
prevlinkage + instance signature) before relay; invalid blocks are dropped at the door. - Vault blobs — pulled by content hash when a peer opts into vault duty; a blob that doesn't hash to a committed diff ref is refused.
- Attestations — verifier co-signatures on heads, ve-weighted.
Serving a resurrection
The peer's highest duty. A keeper on a new device asks the mesh for: the chain from genesis, then the blob set referenced by the surviving diff chain. Any honest spine peer + any complete vault peer is sufficient — the keeper's private seed does the rest locally. Peers never see plaintext at any step.
Honest limits
- NAT traversal and public bootnodes are the same pre-mainnet work they were in v1 — carried, not solved by the rebrand.
- Vault replication is opt-in; a chain whose blobs live on one disk has a provable spine and mortal flesh. The dashboard shows blob redundancy for exactly this reason.