vault_paused: The stablecoin vault is paused
The vault's owner paused it. While the pause lasts, this deployment opens no new budget or stream on the vault, adopts no budget opened from your own wallet on it, and holds back settles of streams that are still running. Nothing is moved: revokes, refunds and releases go on as before, and every signed claim stays settleable.
What to do
- Retry after the pause ends. A pause on contract v2 ends on its own after at most its maximum length.
- Settles that were held back run on the next scheduler pass after the pause.
On the wire
HTTP 409, error type state_error.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "vault_paused",
"message": "…",
"param": "funding",
"doc_url": "…/errors/vault_paused.md",
"fix": "the vault's owner paused it; new budgets, streams and settles wait for the pause to end (funds and signed claims are untouched)"
}
}
Without the header the body has no errorDetail. A child open on the plugin wire (POST /plugin/v1/streams/{id}/children) on a stablecoin budget answers 409 {"error": "child open refused (fail closed)", "reason": "vault_paused"}, never with errorDetail.
See all error codes.