> 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/understanding-the-system/confirmations.md). # Confirmations Confirmation is the one step that turns a priced proposal into a signed transaction, so it's worth being precise about what it means and doesn't mean. ## The rules * **Transaction actions are proposed first.** Nothing is signed at the moment you ask for it. * **Confirmations expire.** A proposal stays open long enough to read and answer, then closes. A stale confirmation is refused, not executed against whatever price happened to be true when you first asked. * **Confirmation is tied to the accepted proposal.** Confirming always re-checks the real cost against what you were shown; if the real terms moved, it fails closed rather than silently charging more. * **Another account cannot confirm your action.** A proposal is bound to the account it was made for. A confirmation from anyone else is refused, as if the proposal didn't exist. * **Changing the terms requires a new proposal.** There's no way to confirm a different action than the one you were shown. * **Repeated confirmation is protected against duplicate execution.** Confirming the same accepted proposal twice — a retry, a doubled message — replays the one result instead of acting twice. ## Example You: `launch $THING paired with XYZ` STONKFUNBOT shows the proposal and its cost, and waits. You: `confirm A1B2C3D4` Only now may execution proceed — against that exact proposal. An arbitrary word like "yes" does not authorize some other, unrelated transaction. Confirmation only ever accepts the one specific proposal it's attached to. ## Why the confirmation window differs by surface The website and Farcaster answer in close to real time, so their confirmation windows are short — long enough to read a proposal and reply, not open-ended. X mentions are checked periodically, so its confirmation window is wider, purely to make sure a genuine reply has time to be seen. In every case, confirming always re-prices against the current terms, so a wider window never means an old price gets honored — see [Confirm](/transaction-flow/confirm.md). --- # 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/understanding-the-system/confirmations.md?ask=&goal= ``` `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.