hop_mandate_mismatch: The hop signs a different child mandate

The delegator signed this hop with a mandateHash (a version 2 hop intent), and that hash is not the child mandate this open resolves. The child mandate is the requested narrowing applied to the delegator's current mandate. Nothing was opened, allocated or held for approval.

What to do

On the wire

HTTP 409, error type state_error.

A stream open (POST /owner/v1/budgets/{id}/streams) or a human payment adds errorDetail only for a client that sends Dynamo-Error-Detail: 1; other clients get {"error": "state", "reason": "hop_mandate_mismatch", "detail": "…"}. The child adoption preparation (POST /owner/v1/streams/{id}/children/adopt-prepare) sends it to every client. The plugin wire's child open (POST /plugin/v1/streams/{id}/children) answers HTTP 409 {"error": "child open refused (fail closed)", "reason": "hop_mandate_mismatch"}, with no detail and no errorDetail.

The detailed body:

{
  "error": "state",
  "reason": "hop_mandate_mismatch",
  "detail": "…",
  "errorDetail": {
    "type": "state_error",
    "code": "hop_mandate_mismatch",
    "message": "…",
    "param": "delegation",
    "doc_url": "…/errors/hop_mandate_mismatch.md",
    "fix": "the hop's mandateHash is not the child mandate this open resolves; recompute it with childMandateHash over the delegator's current mandate and sign again"
  }
}

See all error codes.