> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/10-11-2026-trade-execute-executed-amounts-solana.md).

# 10-11-2026: Execute Reports Confirmation and Executed Amounts on Solana

**Affected endpoint:** `POST /api/v1/trade/execute`

Execute now waits for a same-chain Solana swap to land, as it already does on EVM chains ([05-11-2026](https://docs.nansen.ai/api/changelog/05-11-2026-trade-execute-executed-amounts.md)), and fills `confirmed`, `inputMint`, `inAmount`, `outputMint` and `outAmount`.

* SOL is reported as the wrapped SOL mint, `So11111111111111111111111111111111111111112`, as in the quote. Wrapped SOL the wallet holds counts as SOL.
* Amounts are base units (lamports for SOL) and are what the wallet actually sent and received, after any transfer fee. Network fees, Jito tips and token account rent are not included. In a sponsored swap they are the trader's amounts.
* Same-chain Solana executes take longer, usually by 1 to 2 seconds. Use an HTTP timeout of at least 60 seconds and send `quote_id`.

**Behaviour change:** a Solana swap that failed on-chain is now reported as `status: "Failed"`, with its signature, when the failure is seen before the response. It was previously reported as `"Success"`.


---

# 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.nansen.ai/api/changelog/10-11-2026-trade-execute-executed-amounts-solana.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.
