component · 0x0020 / 0x0021

Public Feed Zone.

The Feed Zone defines named feeds with blockchain-style post chains. Posts live externally on feed servers; the zone holds anchors and checkpoints — small, cryptographically authoritative statements of "this is the real chain."

anatomy of a feed

Each named feed ("main", "announcements", anything you want) has one or more independent chains. Each chain has its own posting keys and a list of checkpoints. A reference to a service in the Service Zone tells clients where the actual post servers are.

why multiple chains

A single chain has a single posting key (or set). If that key is compromised, the chain is poisoned — an attacker can append "real" posts. By supporting multiple independent chains per feed, POZ lets you contain the blast radius:

If chain 1's key is compromised, you POST_TERMINATE chain 1.
You start chain 2 with a fresh key, declared with a GENESIS checkpoint.
Subscribers see the terminate, switch to the new chain.

Checkpoints (GENESIS, VERIFIED, RESUME) let the feed authority declare the authentic chain state and recover from forks.

post types

Type	Effect
`POST_NEW`	New content.
`POST_DELETE`	Marks a previous post as deleted; original preserved.
`POST_REPLACE`	Replaces content; original preserved.
`POST_TERMINATE`	Kills the chain. Posting keys for that chain are no longer accepted.

Posts are immutable. Deletions and replacements are annotations — the original is still there, with a tombstone. This is intentional: history is part of what makes the chain auditable.

the post itself

Each post carries the previous post's hash, a serial number, an author POZ hash, a feed name, a chain ID, a content type and length, and a signature from a key authorized to post on that chain. Verifying a feed is straightforward: walk back to a known checkpoint, check each link.

fig 01 · feeds support multiple independent chains. Terminate the compromised chain; start a fresh one with a new posting key. The feed itself never changes hands.

where posts live

The feed anchor in your POZ record references a service in your Service Zone by hash. That service entry lists the actual feed servers — pool entries with hostnames, ports, priority, and weight. If you change feed providers, the service hash changes, which means anyone watching your feed sees that the infrastructure moved.