Handshake
Peers negotiate identity, features, and the initial trust posture.
Protocol And Replication
Intent first, payload second.
NexusFS synchronizes signed operation knowledge before bulk data. That makes the system more resilient to partial connectivity, delayed blob availability, and audit-oriented verification.
Clock Summary
Each side advertises the highest observed operation counters by device — plus the counters observed above a gap, so one refused operation cannot stall everything behind it.
Ops Batch
Missing operations move first so replicas can understand intended state.
Blob Fetch
Referenced chunk data is requested only when the receiving side needs it — and anything it did not request is dropped, however well it hashes.
Budgeted Passes
The energy scheduler can cap or skip content. A node that took every operation and no bytes still knows what exists and where.
On-Demand Fetch
Reading a deferred file pulls exactly what that read needs, rather than waiting for the next unconstrained pass.
Verification pipeline
- Verify the operation signature, through the same apply path local writes use.
- Check the peer's device key against the one pinned for it.
- Check referenced object and blob hashes against what was requested.
- Drop content that was never requested, however well it hashes.
- Apply policy checks before accepting state.
- Validate the configured proof mode when enabled.
- Store and apply the operation idempotently.