Expand description
§EncodedPostBundleV1 — the server-signed index of posts at a location
A “post bundle” is a server’s durable record of every post accepted into a given
(location_id, time bucket) pair. This is the unit of replication, caching, and
healing on the network — timelines fetch bundles, caches store bundles, and the
two-phase heal protocol reconciles divergent bundles.
The encoding is two parts glued together:
EncodedPostBundleHeaderV1— JSON-encoded, server-signed, enumerating thepost_ids and per-post body lengths the bundle contains, plussealed/overflowedflags, anyhealed_ids, and the publishingcrate::protocol::peer::Peerrecord. This is the bit that proves “server X attests that these posts lived here at time T”.- A concatenation of each
crate::protocol::posting::encoded_post::EncodedPostV1body, in the same order as the header’s post id list.
verify() is exhaustive: it checks the header signature, confirms the sum of
header-declared lengths exactly spans the body, and decrypts each post to verify
its own signature and that its plaintext post_id matches the header’s claim.
Structs§
- Encoded
Post Bundle Header V1 - The server-signed index for all posts accumulated under one (location, time-bucket) key.
- Encoded
Post Bundle V1