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

# Wallet Security Notes

**Every action that moves funds deserves a second look. This page is the second look.**

Wallet actions — deposits, withdrawals, transfers — are the moments where careful trading meets careless approvals and funds disappear. The terminal exposes the controls; verifying the destination, amount, network, and asset is on you.

{% hint style="danger" %}
**Approve nothing on autopilot**

The wallet prompt is the last line of defence. If anything in it doesn't match your intent, **cancel** and re-check.
{% endhint %}

## Before Depositing

Before sending funds to a GraphDex wallet address:

* **Confirm the URL.** You are on the official terminal — bookmark it; don't trust search results.
* **Confirm the network.** Solana ≠ Ethereum ≠ BSC. Wrong network = potential permanent loss.
* **Copy the destination address carefully.** Verify the first and last 4–6 characters by eye.
* **Send only supported assets.** Tokens outside the supported list may be unrecoverable on the GraphDex side.
* **Consider a test transfer first.** A small initial transfer verifies the chain end-to-end before you commit a larger amount.

Funds sent to the wrong network or an unsupported address **may be permanently unrecoverable**. There is no support ticket that fixes a wrong-chain send.

## Before Withdrawing

Before submitting a withdrawal:

* **Confirm the destination wallet address.** Same care as for a deposit.
* **Confirm the asset and amount.** Read every digit; small typos compound.
* **Leave enough balance for network fees.** Some chains require native-asset balance to broadcast.
* **Read the wallet prompt before approving.** The prompt is the source of truth, not the terminal preview.
* **Verify in a block explorer.** When possible, confirm the completed transaction on-chain.

If the destination, asset, amount, or network shown in the wallet prompt doesn't match your intent — **do not approve**. Cancel and start over.

## Transfers Between Wallets

When using **Transfer** to move funds between wallets in your own account:

* Confirm **both sides** of the transfer — source AND destination wallet.
* Match the wallet labels to the strategy / account separation you actually intend.
* Avoid moving funds between wallets while placing time-sensitive trades — the two flows compete for attention.

A misrouted internal transfer is recoverable, but it's still a self-inflicted delay.

## Seed Phrase Safety

GraphDex support, community moderators, and team members **never need your seed phrase**. Anyone asking for it is impersonating support.

* Do not enter your seed phrase into forms, support chats, DMs, or unofficial tools.
* Do not paste it into "wallet recovery" or "wallet verification" sites.
* If your seed phrase was exposed even briefly: treat the wallet as compromised and move funds to a new wallet you control.

## Display Controls Are Not Security Controls

Balance visibility, hidden assets, and hidden transactions affect **what you see in the terminal**. They do **not**:

* Protect funds from on-chain movement.
* Remove assets from the blockchain.
* Hide transactions from anyone watching on-chain.

Display controls are convenience — security is in the wallet, the seed phrase, and the prompt you approve.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/4gAfbZxuoIiP9HWIWRQE"><strong>Assets and Balances</strong></a></td><td>What you hold, in one view.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/rUNLtcMq4Cs8IjCNa3Aw"><strong>Transactions</strong></a></td><td>The history view — verify there after every important move.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/71OY9SZk9Ui76jk5BOF8"><strong>First Safety Checklist</strong></a></td><td>The starter checklist for new accounts.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
Security checks compound. The five seconds you spend verifying a withdrawal prompt save the hours you would spend chasing a misrouted send.
{% endhint %}

## FAQs

<details>

<summary>What if I sent funds to the wrong network?</summary>

Most wrong-chain sends are permanently unrecoverable. Some chains and tokens offer rescue paths, but they're slow and not guaranteed. Always verify the network before a deposit.

</details>

<details>

<summary>Can support recover funds sent to the wrong address?</summary>

No — once a transaction is on-chain, only the holder of the destination address controls those funds. Support cannot reverse on-chain transfers.

</details>

<details>

<summary>Is the wallet prompt the same as what the terminal shows?</summary>

The terminal shows the \*intent\*; the wallet prompt shows what's actually being signed. Always read the prompt — it's the canonical record of what your signature authorizes.

</details>

<details>

<summary>What should I do if I think my wallet is compromised?</summary>

Move funds to a new wallet under a different seed phrase as soon as possible. Treat the compromised wallet as fully exposed — including all approved contract permissions.

</details>

<details>

<summary>Does hiding a transaction protect privacy?</summary>

No. Hidden affects only the terminal display. The transaction is permanently visible on-chain.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/wallet/wallet-security-notes.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.