hop_parent_signer: The parent agent's signer is not reachable here
On the stablecoin escrow (contract v1 or v2), a child stream is opened on chain by the parent stream's serviceNode, with its own key. This deployment has no way to reach that signer, so it cannot open the child for it. The open is refused and nothing is allocated: no hold, no stream row, no authority record.
This replaces the earlier not_found answer for the same case.
What to do
- On a contract v2 budget, open the child from the parent agent's own process, with its own key: prepare it with
POST /owner/v1/streams/:id/children/adopt-prepare, send the preparedopenStreamfrom the parent agent's key, thenPOST /owner/v1/streams/:id/children/adopt(Dynamo-Version1.8.0; see child streams opened by the parent agent). - On either version, run the parent agent on a deployment that can reach its signer, such as a KMS reference or a wallet session key.
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_parent_signer", "detail": "…"}. The plugin wire's child open (POST /plugin/v1/streams/{id}/children) answers HTTP 409 {"error": "child open refused (fail closed)", "reason": "hop_parent_signer"}, with no detail and no errorDetail.
The detailed body:
{
"error": "state",
"reason": "hop_parent_signer",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "hop_parent_signer",
"message": "…",
"param": "delegation",
"doc_url": "…/errors/hop_parent_signer.md",
"fix": "a child open on chain is signed by the parent stream's serviceNode; this deployment cannot reach that signer — the parent agent opens the child from its own process (own hops), nothing was allocated"
}
}
See all error codes.