Use case
Local first, sync later.
The app writes to a log on the device, online or not. When peers meet again, each pulls what it missed, in chunks, and resumes after a restart.
The pieces
The libraries this needs. Each has install steps and a compiled example in its docs.
How it goes
Write on the device
A kolo-log log lives in memory and kolo-store writes each change to disk as one atomic, synced batch. No network is needed to write.
Catch up in chunks
A replica far behind catches up in chunks, each checked by a consistency proof against the root it rebuilt itself.
Resume after a restart
kolo-store keeps the catch-up target with each chunk, so a pull that stopped in the middle picks up where it was.
Good to know
Each peer writes its own log; there is no merge of two writers. An entry over 4 MiB cannot sync, and the log does not sync past it.