Protocol / Consistency / Replication
plannedLayer 1 · Protocol

Replication

The planned peer-to-peer replication of a space's event log across hosts — code is present in tinycloud-core but not yet compiled or mounted. Actively under development.

Replication

Replication is the planned mechanism for synchronizing a space's hash-linked event log across multiple hosts, so the same owner's data can be served by more than one node and survive any single host. It is what turns single-host hosting into a resilient, multi-host space.

Role

Replication is the availability half of hybrid-consistency: it propagates epoch-ordered events between peers and reconciles them by LWW, giving eventual convergence. It is the precondition for multi-host host delegations to be meaningful for data (not just placement).

Mechanics

The subsystem (tinycloud-core/src/replication/mod.rs, with an HTTP surface tinycloud-node-server/src/routes/replication.rs) is present in the codebase but not declared in lib.rs — i.e. not compiled or mounted today. Its design is peer-to-peer sync of the event DAG modeled on Bitcoin/Ethereum-style propagation; note that libp2p in the node is currently used only for ed25519 node identity, not block exchange. This is actively under development outside this checkout.

Relationships

Propagates epoch events; reconciles via conflict-resolution; realizes the eventual half of hybrid-consistency / consistency-model; makes multi-host data real; the roadmap framing (incl. peer discovery) is replication-and-discovery.

Status & drift

Planned / actively under development. Code present but unmounted; no active P2P data sync ships today. See replication-and-discovery.

Sources

  • tinycloud-node: tinycloud-core/src/replication/mod.rs, tinycloud-node-server/src/routes/replication.rs (present, not mounted)