revoked: The stream was revoked

The stream, or one of its ancestors, was revoked by its owner or by the funder. A revocation is permanent and cascades to every descendant. Work that was signed before the revocation stays settleable.

The same code answers:

A payment receipt on a revoked stream never answers revoked: an authorization issued at or after the revoke answers receipt_after_revoke, and a rail execution after the authorization expired answers receipt_expired_authorization (both 409, nothing billed).

A client that does not send Dynamo-Error-Detail: 1 to a 1.3.0 route also sees revoked for stopped, frozen and mandate_amended, so its response shape is unchanged.

What to do

On the wire

HTTP 409, error type halted.

With Dynamo-Error-Detail: 1, and on the routes added in owner-api 1.4.0 and later (for example payment authorizations and receipts) with or without it:

{
  "error": "halted",
  "reason": "revoked",
  "streamId": "stm_…",
  "detail": "…",
  "errorDetail": {
    "type": "halted",
    "code": "revoked",
    "message": "…",
    "param": null,
    "doc_url": "…/errors/revoked.md",
    "fix": "the stream was revoked; open a new stream (a revocation is permanent)"
  }
}

On the older routes without the header, including the plugin wire's meter, the body has no errorDetail.

See all error codes.