offer_unsigned: The hop carries no signed payee offer
The deployment requires own hops, and the open carries no payeeOffer; or the hop is a human payment's consent-attributed root, which always needs the payee's signed offer. (A hosted top-up without an offer, where one is required, answers topup_payee_offer_required instead.) The payee states which categories it offers, signed with its own key. The open is refused and nothing is allocated.
What to do
- Have the payee sign the categories it offers with
signPayeeOfferand send it aspayeeOffer.
On the wire
HTTP 409, error type state_error.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"reason": "offer_unsigned",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "offer_unsigned",
"message": "…",
"param": "delegation",
"doc_url": "…/errors/offer_unsigned.md",
"fix": "this deployment requires a signed payee offer; the payee signs the categories it offers (signPayeeOffer)"
}
}
Without Dynamo-Error-Detail: 1 a stream open or a human payment receives the same body with no errorDetail. A child open on the plugin wire (POST /plugin/v1/streams/{id}/children) answers 409 {"error": "child open refused (fail closed)", "reason": "offer_unsigned"}, never with errorDetail.
The child adoption preparation on contract v2 (POST /owner/v1/streams/{id}/children/adopt-prepare) checks its payeeOffer the same way and sends errorDetail to every client.
See all error codes.