> For the complete documentation index, see [llms.txt](https://docs.zvaultmarketplace.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zvaultmarketplace.xyz/networks-and-custody.md).

# Networks and Custody

ZVault currently connects a **ZSA test-network NFT** with **Zcash mainnet ZEC payments**. This split is important to understand before trading.

| Question                                            | Current design                                                                  |
| --------------------------------------------------- | ------------------------------------------------------------------------------- |
| Where is the NFT?                                   | On the ZSA test network used by this release.                                   |
| What pays for a trade?                              | Real ZEC on Zcash mainnet.                                                      |
| Is payment and NFT delivery one atomic transaction? | No. They are separate transactions and steps.                                   |
| Who initiates the NFT settlement?                   | The marketplace service uses managed ZSA custody and queues the asset transfer. |

## Typical transaction states

| State                  | Meaning                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------ |
| **Active**             | A listing or offer is open.                                                                |
| **Awaiting payment**   | A trade was accepted and the buyer must send the required ZEC payments.                    |
| **Payment confirming** | Both payment references were submitted; confirmation and seller action are still required. |
| **Settlement queued**  | The marketplace accepted the confirmation and queued the NFT transfer.                     |
| **Settled**            | The marketplace recorded completion of the NFT transfer.                                   |
| **Failed or expired**  | The action needs review or has passed its allowed time.                                    |

## What payment verification checks

The current backend is designed to check mainnet transaction IDs, recipient outputs, exact amounts and a configured number of confirmations. It also requires the seller's confirmation before queuing the NFT transfer.

{% hint style="warning" %}
This does **not** turn the two-network process into an atomic swap. If the NFT transfer does not settle after payment, contact support so the trade can be reviewed.
{% endhint %}

For a guided example, see [Buy an NFT](https://docs.zvaultmarketplace.xyz/buy-an-nft.md).


---

# 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.zvaultmarketplace.xyz/networks-and-custody.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.
