STELLAR_TX_DEPLOY_PRE_APPROVED

Hand-crafted deploy rejected: milestones cannot be born approved, released, resolved or disputed.

422 Validation Error · request handling

Example

{
  "type": "https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/stellar-tx-deploy-pre-approved",
  "title": "Validation Error",
  "status": 422,
  "code": "STELLAR_TX_DEPLOY_PRE_APPROVED",
  "detail": "Hand-crafted deploy rejected: milestones cannot be born approved, released, resolved or disputed.",
  "instance": "/…",
  "traceId": "…"
}

When it happens

A hand-crafted deploy carries milestones with lifecycle state already set at birth: the v1 approved/released/resolved/disputed booleans, or the v2 approvals struct with a non-zero approval_count or a non-empty approved_by. Approval and release must only ever happen through the escrow's own methods with the right signer's auth.

How to fix it

Deploy milestones in their initial state (no approvals, not released, not disputed). Transactions produced by the build endpoints always comply.