> 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/faq.md). # FAQ ### Why is Phantom showing a smaller SOL change than “Requesting”? Accept often **deposits and executes in one transaction**. Phantom shows the **net** wallet change. Example: deposit 2 SOL, receive 1 SOL → about **−1 SOL** net. ### Why do instructions say “Unknown”? Phantom has not decoded the Niftix program IDL. Review the balance change and that the site origin is correct. ### Can I put SOL on both sides? Yes — one SOL amount per side. Duplicate token/NFT mints across sides are not allowed. ### Why don’t I see my NFTs? App cluster must match the wallet network; unsupported types (e.g. cNFTs) won’t list; try a refresh. ### Who can cancel? Usually the **creator**, until the counterparty deposits requesting assets (including after accept). Once they have deposited, use expiry / withdraw. ### Are fees charged on NFTs and USDC? Yes, at execute: * **SOL:** 0.25% per SOL leg (capped at 0.25 SOL) * **USDC / SPL:** 0.25% per SPL leg (capped at 0.25 USDC) → treasury ATA * **NFT / Core:** 0.01 SOL **once per side** that includes any NFT or Core (not per NFT), paid by the execute signer ### Firm offer vs Open to offers? **Firm** = fixed terms. **Open to offers** = discuss in Trade Chat, then change terms with a new on-chain offer if needed. ### Is chat binding? No. Only signed on-chain transactions move assets. --- # 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/faq.md?ask=&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.