20. Encryption keeps the shape
You seal payloads, paths are sealed one part at a time so prefixes survive, timestamps and ids stay plain, and relays can merge what they cannot read. Post note: capability tokens travel in the clear too.

20. Encryption keeps the shape

You seal payloads, paths are sealed one part at a time so prefixes survive, timestamps and ids stay plain, and relays can merge what they cannot read. Post note: capability tokens travel in the clear too.

It is how a server can carry your data without learning what it is.

You can let a server carry your data without reading it.

You encrypt the payload. The server sees a parcel it cannot open.

The path is encrypted one part at a time. Blog, ideas, game become three scrambled parts.

Two paths that share a prefix still share it after scrambling. So prefix pruning and areas keep working on data nobody can read.

Timestamps stay plain, because newer wins has to compare them. The ids stay plain too. The server can relay and merge, and never learn what any of it says.

Check yourself. Why are timestamps left unencrypted?

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Attributes
name
20. Encryption keeps the shape
summary
You seal payloads, paths are sealed one part at a time so prefixes survive, timestamps and ids stay plain, and relays can merge what they cannot read. Post note: capability tokens travel in the clear too.