> For the complete documentation index, see [llms.txt](https://docs.palliora.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.palliora.org/defi/learn/concepts.md). # Concepts


Shielded accounts	Your private account, derived from your wallet. Two key pairs and a root address, and how others find you.
Notes and commitments	How value is stored as notes, how the commitment tree tracks them, and how nullifiers stop a note being spent twice.
Shielded transactions	Deposit, transfer, withdraw and adaptor call. What each one proves and what the pool checks.
Relaying and gas	How a transaction is submitted without exposing your wallet, and how the fee is paid from your shielded balance.
Adaptors	How a private transaction swaps, lends or stakes through another protocol without changing that protocol.
Accountable privacy and disclosure	How a revoker and Decom guardians can de-anonymize one transaction, and how you can share a view key yourself.
Palliora integration	How a revoker keeps a de-anonymized transaction on Palliora Data Availability, and who can read it.
Private Sub-accounts	How you trade on Hyperliquid with private funding, and what stays public.
Cryptographic primitives	The curve, the proof system, the hashes and the encryption the protocol uses.
Privacy model	What is hidden, what is public, and what limits the privacy you get.

--- # 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.palliora.org/defi/learn/concepts.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.