Expand description
§EncodedPostV1 — individual post wire format
The canonical on-the-wire representation of a single user post.
EncodedPostV1 pairs:
- an
EncodedPostHeaderV1carrying the author’s keys, timestamp, linked base IDs, and signing-authority choice, - the post body bytes (compressed + encrypted),
- an Ed25519 signature (or delegated-key signature per
PostSigningAuthorityV1).
The post_id is the hash of the signature, which gives every post a deterministic,
collision-free identifier derivable from the bytes alone. On the wire both header
and body are compressed and encrypted under passwords derived from the client id
and the set of linked base IDs — so that recipients who already know those keys
can decrypt without an extra key exchange.
EncodedPostV1::bytes_without_body returns just the header bytes, so that
previews and timeline skeletons can be delivered before the full body is paid for
in the reader’s bandwidth budget.
Structs§
- Encoded
Post Bytes V1 - Encoded
Post Header Signature Delegation V1 - Encoded
Post Header Signature Direct V1 - Encoded
Post Header Signature Ephemeral V1 - Encoded
Post Header Signature Mechanism V1 - Encoded
Post Header V1 - Encoded
Post V1 - A single user post in its canonical, verifiable form as it travels across the network.