Part of Stem. This page defines the rpc/type/rejection message type used by the sync RPC specification. It is also the shape of a stashed entry, where the reason is a missing dependency or authority.

The formal schema is attached as the schemaDefinition of this page.

Why a blob was refused, or why it was stashed instead of applied. The two missing-* reasons are the stash reasons; they appear in stashed lists, never in rejected lists.

Fields

field	type	required	meaning
`cid`	cid	yes	The blob concerned.
`reason`	one of `"invalid"`, `"unauthorized"`, `"out-of-scope"`, `"not-wanted"`, `"too-large"`, `"missing-dependency"`, `"missing-authority"`	yes	Why.

Rules

invalid covers bad encoding, bad signature, a structural rule of the kind, or a hash mismatch.

unauthorized means the signer holds no authority for the claimed scope at the time of evaluation. In a Publish response under stashed it means the authority may still arrive.

out-of-scope means the blob is valid but does not belong to the claimed scope.

not-wanted means the receiver's policy does not accept the scope.

An Offer receiver may choose to report fewer reasons than it knows; it never reports a reason that would reveal what it already holds.

Today (HM24)

HM24 stashes with reasons FailedPrecondition, PermissionDenied and BadData, and fails a whole StoreBlobs batch on any rejected blob. Stem reports per blob.

Example

{"cid": {"/": "bafy…33"}, "reason": "out-of-scope"}

Fields

Rules

Today (HM24)

Example

See also