> For the complete documentation index, see [llms.txt](https://deenz.gitbook.io/bq-core/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deenz.gitbook.io/bq-core/using-the-bqsdk/bqsdk/solve-mode/sending-tx.md).

# Sending a solution transaction

Generating a solving proof for an already defined *bqTest* in solve mode (*solveModeTest*) proves that you know a *certain* solution. You will need the smart contract to verify whether this solution is valid, and grant you the credential if so. You can send a solution transaction by doing:

```js
await solveModeTest.sendSolutionTransaction( 
    signer,
    proof
)
```

Where *proof* is the result of [generating a proof](/bq-core/using-the-bqsdk/bqsdk/solve-mode/generating-proof.md), and *signer* is a valid [ethers.Signer](https://docs.ethers.io/v5/api/signer/), which corresponds to the account that will send the solving transaction.

Note that the account that sends the solving transaction is not necessarily the account that *receives* the credential. The recipient of the credential, also known as the *solver*, is embedded in the proof itself. This means that anyone can post someone else's proof without risk of cheating, allowing for transaction relaying to be built on top.


---

# 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://deenz.gitbook.io/bq-core/using-the-bqsdk/bqsdk/solve-mode/sending-tx.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.