Peering, identity, and the ledger

Peer-to-peer mesh IMPLEMENTED

Nodes form a libp2p mesh with no central server. The transport stack is:

• Noise XX — encrypted transport.
• Yamux — connection multiplexing.
• Kademlia DHT — cross-network discovery.
• gossipsub — topic-based message propagation.
• relay — circuit relay for NAT traversal.

src/network/, src/node.rs

Identity IMPLEMENTED

A node holds a persistent Ed25519 keypair; the public key derives its PeerId. Keys live on disk (~/.lattice). There is no TPM requirement and no cloud-held identity — a node's key is plain Ed25519 on the operator's machine.

src/node.rs, src/network/protocol.rs

Bootstrap and discovery IMPLEMENTED

A joining node dials a bootstrap relay multiaddr, then discovers peers through Kademlia and mDNS (mDNS can be disabled with --no-mdns). Relay circuits carry traffic for nodes that cannot be dialed directly.

src/network/, src/node.rs

The hash-chain ledger IMPLEMENTED

Commitments form an append-only Blake3 hash chain. Frames carry a height and, in newer frame versions, an authority-certificate trailer. The chain is the single source of committed truth; economic transactions gossip separately (see Economics).

src/commit.rs, src/ledger/types.rs