> 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/verify.md). # Verify A transaction being submitted is not the same as it succeeding. STONKFUNBOT waits for Solana to actually confirm the result before reporting anything back to you. ## What this means in practice * **Success is reported only once the chain confirms it.** A submitted-but-unconfirmed transaction is never described as done. * **Failure is never shown as success.** If the network rejects a transaction, or it can't be confirmed, you're told that plainly. * **Ambiguous outcomes are handled conservatively.** When it genuinely can't be told whether something landed, STONKFUNBOT doesn't guess in either direction — see [Failures & Recovery](/understanding-the-system/failures-and-recovery.md). ## Why this is a separate step A launch or a swap isn't something to assume happened just because a signature was produced and sent. Network conditions can delay or drop a submission. Treating "submitted" and "confirmed" as the same thing is exactly the kind of shortcut that produces a false "it worked" — so STONKFUNBOT doesn't take it. Once verified, the result is recorded, and that's what you see — a launched token's on-chain link, or a completed swap's outcome. --- # 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/verify.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.