protocol_fee_mismatch: The vault's fee differs from the configured fee

The deployment reads its protocol fee from one place, the revenue switchboard, and checks it against the fee the vault charges. The vault's fee changed and no longer matches. New stablecoin budgets and streams, and adoptions of budgets opened from your own wallet, are refused until the two agree. Streams already open on contract v2 keep the fee they opened with.

At start-up the same check (under this code) refuses to start the deployment, with a message naming the vaults and their fees: when two configured vaults charge different fees and no fee is configured, or when a vault's fee differs from the fee the switchboard expects. No HTTP answer is sent then.

What to do

On the wire

HTTP 409, error type state_error.

With Dynamo-Error-Detail: 1:

{
  "error": "state",
  "detail": "…",
  "errorDetail": {
    "type": "state_error",
    "code": "protocol_fee_mismatch",
    "message": "…",
    "param": "funding",
    "doc_url": "…/errors/protocol_fee_mismatch.md",
    "fix": "the vault's fee differs from the switchboard's; the operator sets CORE_REVENUE_SWITCHES contract_fee.bps to the vault's fee and restarts"
  }
}

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": "protocol_fee_mismatch"}, never with errorDetail.

See all error codes.