> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/getting-started/first-transaction.md).

# Your first Vultisig transaction

Send or receive your first transaction in Vultisig. Check the address before you sign.

Once the vault exists and you have a backup, you can receive and send.

***

## Receive

1. Open your vault
2. Tap the asset you want to receive
3. Tap **Receive** or the QR icon
4. Copy the address, or show the QR to the sender

{% hint style="info" %}
Each chain has its own address. A Bitcoin address will not receive Ethereum.
{% endhint %}

You can deposit from another wallet, an exchange, or a friend.

***

## Send

1. Select the asset you want to send
2. Tap **Send**
3. Paste the recipient, scan a QR, or pick a saved address
4. Enter the amount, or tap **Max**
5. Check destination, amount, and fee
6. Sign with your devices
7. The app broadcasts after a successful signature

Check the address before you sign. Once it is on-chain, you cannot undo it. For a large first send to a new address, send a small test first. Leave a little native token in the vault for the network fee (ETH, BTC, SOL, and so on).

Full send path: [Send crypto from Vultisig](/app-guide/wallet/sending.md).

***

## Signing

On a Fast Vault, you approve on your device and VultiServer co-signs. On a Secure Vault, your other device has to join.

1. Start the transaction on one device
2. Pair the other device(s) by QR or relay
3. Every device shows the same destination, amount, and (on EVM) decoded function
4. Each device approves on its own
5. The shares combine into one signature
6. The app broadcasts

No device holds the complete key. One compromised device cannot move funds.

[How Vultisig signs a transaction](/security-and-technology/keysign.md)

***

## Next

| Action   | Guide                                     |
| -------- | ----------------------------------------- |
| **Send** | [Sending](/app-guide/wallet/sending.md)   |
| **Swap** | [Swapping](/app-guide/wallet/swapping.md) |
| **DeFi** | [DeFi](/app-guide/defi.md)                |

***

## If something goes wrong

**Stuck after broadcast.** Check the chain explorer. Busy networks and low fees delay confirmation.

**Signing failed.** Same Wi-Fi or the relay, matching vault name, latest app. Try the sign again.

* [FAQ](/help-and-legal/faq.md)
* [Discord](https://discord.gg/Cugw9T2NrP)


---

# 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.vultisig.com/getting-started/first-transaction.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.