> 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/transaction-verification.md). # Transaction Verification "Verification" happens at two different points in an action's life, and this page separates them. ## Before signing: inspecting the transaction A transaction prepared by an upstream service (like the launchpad) or built internally (like a swap) is decoded and checked before your wallet ever signs it. STONKFUNBOT does not trust that an upstream service's transaction does only what it claims — it verifies the transaction's actual contents against what you were quoted. What gets signed is then bound to what was checked: the exact transaction that passed inspection is the one submitted, not a different one substituted afterward. ## After submission: confirming on-chain Submitting a signed transaction to Solana isn't the same as it succeeding. STONKFUNBOT waits for the network to actually confirm the result before reporting anything back to you — see [Verify](/transaction-flow/verify.md). ## Why both matter Checking the transaction before signing catches a bad or unexpected transaction before it can be submitted at all. Confirming after submission catches network-level uncertainty — a transaction that was sent but whose outcome isn't yet known. Skipping either one would mean trusting a step that can be verified instead. --- # 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/transaction-verification.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.