# Send Transactions

The **Send Transactions** feature allows users to perform transactions by prompting in plain English such as "Hey Brian, can you swap 100 usdc for eth on Polygon?".

{% hint style="success" %}
The **Send Transactions** feature is **non-custodial**. 

You still have to sign the transaction with your wallet, **Brian is not** a custodial solution managing your private key.

**Please read carefully the transaction you're executing!**
{% endhint %}

## How to send a transaction

1\) <mark style="color:red;">**Connect your EOA Wallet**</mark>. We suggest using Rabby Wallet for a smoother UX, and you can check the transaction simulation within the wallet extension.

<figure><img src="/files/ku4kEv3WRFnWf5YS0yvV" alt=""><figcaption></figcaption></figure>

2\) <mark style="color:red;">**Sign the**</mark> [<mark style="color:red;">**Terms and Conditions**</mark>](https://brianknows.org/terms-and-conditions) <mark style="color:red;">**message**</mark>. Read carefully the [terms and conditions](https://brianknows.org/terms-and-conditions) related to using real funds on the Brian App and the prompt-to-earn program.

3\) <mark style="color:red;">**Check the available networks**</mark>**,** by clicking on the button on the bottom-left. On the Brian App we support Ethereum and the other main networks in the EVM ecosystem.

<figure><img src="/files/YwukAiyymobRAPBmNSVp" alt="" width="375"><figcaption></figcaption></figure>

4\) <mark style="color:red;">**Check the supported actions actions**</mark>. For each chain, we support specific actions (for example, the ENS registration is only supported on Ethereum). By clicking on one action, you have an example of the prompt for that action. For the same action, you can write it in so many different ways!

<figure><img src="/files/02t9rqMTb6uaaV9JDSzm" alt="" width="318"><figcaption></figcaption></figure>

5\) <mark style="color:red;">**Prompt your intent**</mark>. When you confirm the prompt, you're not executing the TX! Brian will first extract your intent into parameters and then build the TX via a series of solvers/aggregators like LIFI, Enso Finance, or Bungee Exchange.

<figure><img src="/files/FCFRZ6in7vcgTtaQw2Ju" alt=""><figcaption></figcaption></figure>

6\) <mark style="color:red;">**Read the transaction description and review everything in the TX info box**</mark>. When you have reviewed everything, you can confirm the TX, and, as in any dapp, the EOA wallet extension will pop up.

{% hint style="warning" %}
Read the transaction description carefully and review all the parameters before executing the TX. **You're aware that you're solely responsible for what happens to your funds after the TX executio**n.
{% endhint %}

a) <mark style="color:orange;">**Transaction description**</mark>: a human-readable description of the TX you are executing.

<figure><img src="/files/kvtAVjTSL4V7G7QaaHA5" alt=""><figcaption></figcaption></figure>

b) <mark style="color:orange;">**Transaction info**</mark>: you can manually check each of the parameters involved in the transaction. For example, for a swap, the involved tokens, protocols, and the sender and receiver addresses.

<figure><img src="/files/IGIxT8MgF3Y2NQmSn9aG" alt="" width="375"><figcaption></figcaption></figure>

&#x20;7\) <mark style="color:red;">**Sign the transaction in your EOA wallet**</mark>**.** This will normally imply an approve + execute in the case of an ERC20-related action (like a swap or bridge) or just one TX in the case of using ETH.

Let's make the example with a swap of an ERC20:\
7.1) <mark style="color:orange;">**Approve**</mark>

<figure><img src="/files/GhDC07OuKG8lpgdbkEol" alt="" width="375"><figcaption></figcaption></figure>

7.2) <mark style="color:orange;">**Swap**</mark>: on Rabby, you can easily see, thanks to the TX simulation, the tokens that I'm sending and the ones I'll receive. Plus, there is a lot of other info for the transaction.

<figure><img src="/files/FpRwpJG8RZosqtLx3pWW" alt="" width="375"><figcaption></figcaption></figure>

8\) <mark style="color:yellow;">**Congrats, you have performed your first swap on the Brian app!🎉**</mark> Now, by clicking on the "block explorer" button, you open the block explorer on that chain and can see that the transaction has been executed correctly.

<figure><img src="/files/vSazSVWTpD954h3Q4bxe" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.brianknows.org/brian-app/send-transactions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.