> For the complete documentation index, see [llms.txt](https://arbydex.gitbook.io/arbydex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbydex.gitbook.io/arbydex/security/wallet-address-safety.md).

# Wallet Address Safety

### Always Verify the Destination Address

A wallet address identifies where blockchain assets are sent.

Because blockchain transfers may be irreversible, entering the wrong address can result in permanent loss of funds.

#### Before Sending

Always verify:

```
Destination Address
        ↓
Supported Asset
        ↓
Network
        ↓
Amount
        ↓
Transaction Details
        ↓
Confirm
```

#### Copy and Paste Carefully

When copying a wallet address, always compare the copied address with the intended destination.

Do not assume that an address is correct simply because it was copied successfully.

#### Address Replacement Risk

Malicious software or browser extensions can potentially interfere with copied wallet addresses.

For important transactions, compare the destination address carefully before confirming.

#### Test Transfer

When appropriate, consider sending a small test amount before making a large transfer to a new destination.

This can help verify that the destination address and network are correct.


---

# 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://arbydex.gitbook.io/arbydex/security/wallet-address-safety.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.