> 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/how-it-works.md).

# How it works

ZVault connects a marketplace interface, Noir Wallet, a ZSA asset network and a ZEC payment network. Each part has a different job.

![ZVault's marketplace components and two network paths](https://content.gitbook.com/content/Bur6Xv3EO0mNKZgCbJWb/blobs/DGmVl7Dcx5Rd38LexQ1u/.gitbook/assets/01_overview.png)

| Component               | Role in the experience                                                         |
| ----------------------- | ------------------------------------------------------------------------------ |
| **ZVault website**      | Displays NFTs, listings, offers, transaction states and wallet activity.       |
| **Noir Wallet**         | Connects the user and asks for approval when an action or payment is required. |
| **ZSA test network**    | Carries the NFT asset used by this version of the marketplace.                 |
| **Zcash mainnet**       | Carries real ZEC payments for a completed marketplace trade.                   |
| **Marketplace service** | Records signed actions, payment references and NFT settlement progress.        |

## One trade, two network paths

A buyer pays real ZEC on mainnet. Separately, the NFT is transferred on the ZSA test network. The marketplace service coordinates those steps. The current flow is **not an atomic swap**: payment and NFT transfer do not happen in one indivisible blockchain transaction.

The asset side uses marketplace-managed custody during settlement. This is a material part of the current design, so a user should wait for the NFT settlement status rather than treating a wallet payment confirmation as proof of ownership transfer.

## What a completed trade means

The app must receive the required payment transaction references, verify the applicable payment outputs and confirmations, obtain the seller's confirmation, and complete the separate NFT transfer. Only then should the buyer consider the marketplace transfer finished.

For the current release boundary, see [Networks, custody and transaction status](https://docs.zvaultmarketplace.xyz/networks-and-custody.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/how-it-works.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.
