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

# Security & risks

{% hint style="danger" %}
Crypto swaps are irreversible once executed. Only trade assets and counterparties you understand. Niftix escrow reduces counterparty deposit risk — it does not remove market, wallet, or phishing risk.
{% endhint %}

## What escrow protects

* Your offering assets sit in a program vault until rules allow settle, cancel, or expire recovery.
* Private offers enforce the designated receiver wallet on-chain.
* Fee and treasury for a swap are snapshotted at create time.

## What escrow does **not** guarantee

* That an NFT’s off-chain metadata or “floor” is accurate.
* That a counterparty will accept before expiry.
* Protection if you sign a malicious transaction outside Niftix.
* Support for compressed NFTs or Token-2022.

## Good habits

1. Verify mint addresses and amounts on the review screen.
2. Match wallet network to the app cluster.
3. Prefer hardware / cold storage for large holdings; use a hot wallet with limited funds for trading.
4. Never paste seed phrases into the site or chat.
5. Read [Terms of Service](https://niftix.app/legal/terms) before trading.

## Program ID

Always confirm you are interacting with:

```
46pyskaPyNGtne3UaYuVBZbjUVaP9EUtF9Zfc2krghTj
```

on the intended cluster (devnet vs mainnet-beta).


---

# 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://niftix.gitbook.io/niftix-docs/safety/security-and-risks.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.