Part of Stem. This page defines the disclosure record, the outbound half of privacy bookkeeping.

A disclosure says: I served this blob to that peer at this time because of this basis.

Fields

field	type	required	meaning
`blob`	CID	yes	The blob served.
`peer`	peer id	yes	The receiving peer.
`ts`	timestamp	yes	When, by the serving peer's clock.
`basis`	basis	yes	Why the serve was allowed.

Rules

Every blob served by Fetch, by the web gateway or by the local API to a non-local caller is recorded. Public serves may be aggregated per peer per day to bound the ledger; non-public serves are always recorded individually. The ledger is local state: it is never synced and never revealed to other peers, and ListDisclosures is available only to the daemon's owner. Its purpose is to answer, after a revocation or a mistaken share, exactly who already holds the bytes. Retention of the ledger is a local setting.

Today (HM24)

Nothing. Once bytes have replicated there is no record of where.

Example

{
  "blob": {"/": "bafyreidraftgenesischange00000000000000000000000000000000"},
  "peer": "12D3KooWRxtB3kQ7q2fZ5mXvN9pLaW4cJ8uHsYdE2gV6iTbMnKoP",
  "ts": 1759910700000,
  "basis": {"kind": "grant", "account": {"/": {"bytes": "7QEE...Collaborator"}}, "grant": {"/": "bafyreigrantcollaboratorread0000000000000000000000000000000"}}
}

Fields

Rules

Today (HM24)

Example

See also