Basis
Why a peer was allowed to receive a blob, recorded with every disclosure, as public, a grant held by an authenticated account, a bearer secret, a site relationship, or an offer round trip.
Fetching schema…

Part of Stem. This page defines basis, the union recorded in a disclosure.

A basis is the reason a serve was allowed, precise enough that a revocation can find every disclosure it affects.

Variants

kind

fields

meaning

public


the blob was readable by everyone

grant

account, grant

the peer authenticated as account, which a live grant put in the blob's audience

bearer

grant

the peer presented the secret of a live bearer grant

site

space, grant

the peer is the space's declared site and holds the sync grant

offer

request

the blob was served back to the peer that had just offered it

Rules

The serving peer records the basis at serve time, with the grant CID that justified it. When a grant is revoked, ListDisclosures filtered by that grant lists every peer that received bytes under it, which is the honest statement of what revocation can and cannot do. The offer basis exists because the receiver of an offer fetches from the offerer, which is a serve in the opposite direction.

Today (HM24)

No record is kept of why a blob was served; the decision is made and forgotten.

Example

{"kind": "grant", "account": {"/": {"bytes": "7QEE...Collaborator"}}, "grant": {"/": "bafyreigrantcollaboratorread0000000000000000000000000000000"}}

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

Unsubscribe anytime