> For the complete documentation index, see [llms.txt](https://docs.stonkfun.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stonkfun.bot/transaction-flow/execute.md).

# Execute

Execution only begins after your confirmation is accepted. Nothing in this step involves further judgment calls — it's deterministic, from here to submission.

## What happens

1. **Inspection.** The prepared transaction is decoded and checked before it's trusted — never signed blind based on what an upstream service says it does. See [Transaction Verification](/understanding-the-system/transaction-verification.md).
2. **Binding.** What gets signed is proven to be the exact transaction that was checked and the exact terms you confirmed — not something swapped in afterward.
3. **Signing.** Only a transaction that passed every check is signed, by your own wallet.
4. **Submission.** The signed transaction is submitted to Solana.

## Guardrails

A hard cap bounds how much a single signed transaction can move out of your wallet, independent of what any proposal claims. A repeated or replayed confirmation is recognized and returns the original result rather than executing again.

## Next

Execution isn't the end of the story — see [Verify](/transaction-flow/verify.md) for what happens before you're told anything succeeded.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stonkfun.bot/transaction-flow/execute.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.