vault_owner_unqualified: The vault's owner is not a qualifying multisig
A stablecoin deployment runs only while its vault is owned by a Safe multisig with a threshold of 2 or more. Ownership moved to an address that does not qualify: a plain account, a delegated account, a contract without a threshold, or a Safe with a threshold of 1. New stablecoin budgets and streams, and adoptions of budgets opened from your own wallet, are refused until it qualifies again. Running streams keep settling. A local development chain is exempt from this check.
What to do
- Move the vault's ownership to a Safe with a threshold of 2 or more. The next scheduler pass picks up the change.
On the wire
HTTP 409, error type state_error.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "vault_owner_unqualified",
"message": "…",
"param": "funding",
"doc_url": "…/errors/vault_owner_unqualified.md",
"fix": "the vault's owner is no longer a Safe with threshold >= 2; new money-mode opens wait until ownership moves to a qualifying Safe"
}
}
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_owner_unqualified"}, never with errorDetail.
See all error codes.