> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/stellar/stellar-tx-deploy-fee-above-ceiling.md).

# STELLAR\_TX\_DEPLOY\_FEE\_ABOVE\_CEILING

Hand-crafted deploy rejected: platform\_fee above the ceiling would lock every deposit in the escrow.

`422 Validation Error` · request handling

### Example

```json
{
  "type": "https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/stellar-tx-deploy-fee-above-ceiling",
  "title": "Validation Error",
  "status": 422,
  "code": "STELLAR_TX_DEPLOY_FEE_ABOVE_CEILING",
  "detail": "Hand-crafted deploy rejected: platform_fee above the ceiling would lock every deposit in the escrow.",
  "instance": "/…",
  "traceId": "…"
}
```

### When it happens

A hand-crafted transaction (deploy or update) carries a `platform_fee` above 9,970 bps. Beyond that ceiling the contract computes a negative net transfer on release, so every deposit locks in the escrow permanently — the API refuses to relay it.

### How to fix it

Keep `platformFee` at or below the ceiling (platform fee + the 0.3% Trustless Work fee must not exceed 100%). Transactions produced by the build endpoints always comply.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/stellar/stellar-tx-deploy-fee-above-ceiling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.