Knolo KIP-0028 and KIP-0029: Signed Exchange Offers and Capsules
Knolo KIP-0028 signs an offer for one Knowledge Image to one recipient; KIP-0029 capsules show objects belong to that image. What each binds and refuses to claim.
Knolo is the open-source, local-first Knowledge Image runtime and format, released under Apache-2.0 and published on npm as @knolo/core. Two new Knolo Improvement Proposals landed in the open repository on 12 November 2026: KIP-0028, Exchange Offer V1, and KIP-0029, Exchange Capsule V1. Both carry the status "foundation implementation", and both ship in @knolo/core 6.2.2.
This note looks at them as specifications: what each one binds, what each one refuses to claim, and how they fit the rest of the Knolo specifications.
Knolo KIP-0028: a signed offer for one image and one recipient
KIP-0028 defines a signed offer, an accept or reject decision, and a receipt for handing one complete V5 Knowledge Image to one named recipient. It is explicitly not a sync request; KIP-0014 remains the replica-sync message, and KIP-0028 does not change stateRoot, objectRoot or the sync wire codec.
Every message is canonical CBOR, signed with Ed25519 over the payload without the signature bytes. An offer binds the sender and recipient principals, the artifact kind (knowledge-image in this version), the artifact SHA-256, stateRoot and size, an optional namespace, a nonce and a validity window. The offerId is a domain-separated digest over those fields. A copied offer still names one recipient, and the recipient's host must pass that principal as the expected recipient.
The receipt records the role, the artifact identity, the decision, a verification code and a policy label. verified requires accept, so a rejection can never be recorded as verified. The codes are deliberately specific: verified, digest-mismatch, state-root-mismatch, expired, replay, unauthorized-recipient, revoked-key, policy-denied, mount-failed, oversized and interrupted.
Knolo replay and key rules fail closed
The artifact check runs in a fixed order: size, SHA-256, V5 mount, then stateRoot. Only after the offer and the artifact both verify is the offerId admitted to the replay cache. A failed transfer does not consume a replay entry, and a second admission of the same id fails. Keys are resolved by principal and key id; a revoked key, a key outside its validity window, or a missing or ambiguous key all fail.
Core takes now from the host and never reads a clock, a socket or the filesystem. Sockets, TLS, peer URLs, policy files and cache paths belong to the host package, which today is @knolo/exchange 0.1.0.
Knolo KIP-0029: capsules are evidence, not a Merkle proof
A capsule is evidence that a few objects belong to one verified V5 Knowledge Image. It carries the V5 commit record, the full sorted object-id list, and up to 64 selected object records. Verification recomputes each selected object id, recomputes objectRoot from the full id list, and recomputes stateRoot from the carried commit. That stateRoot must match both the capsule and the signed KIP-0028 offer.
The specification is plain about its limits. In a V5 image, objectRoot is a flat digest of the sorted object ids, not a Merkle tree, so a capsule does not claim a Merkle inclusion proof. Receiving a capsule does not mount a store, adopt an image or activate instructions, and the codec does not run KAR, Cortex or a model.
How Knolo checks compatibility
Both KIPs come with conformance cases in the repository, under conformance/exchange/v1 and conformance/capsule/v1. They build a V5 image in process and check fail-closed results, and they do not replace the existing V5 image fixtures. That keeps the bar the same as the rest of the Knolo compatibility work: a runtime is compatible when it produces the same results on the same bytes.
KIP-0028 also lists what it leaves out: partial segment transfer, automatic adoption and skill activation. Diverged images stay on the KIP-0013 and KIP-0015 path. Those boundaries are the point of a "foundation implementation" status, and the Knolo lifecycle page describes how proposals move from there.
Read the Knolo specs yourself
- Browse the Knolo KIP index on knolo.org and the Knolo verify page.
- Read
spec/KIP-0028-exchange-offer-v1.mdandspec/KIP-0029-exchange-capsule-v1.mdin the Knolo core GitHub repo. - Try the
knolo exchangecommands with the Knolo developer docs on knolo.dev.
Verification in Knolo is about integrity, not truth: a verified offer proves which bytes moved, not that their contents are correct. Knolo is built in the open by Hive AI under Apache-2.0.
knolo · kips · specifications · exchange · verification
