> 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/build/build.md).

# Overview

Palliora DeFi (formerly Veilnyx) gives you three things to build with: an SDK that creates and proves private transactions, a pool contract that checks them, and an adaptor interface that lets a private transaction use another protocol.

This section is for developers and for AI coding agents. If you only want to use the app, open it at [defi.palliora.org](https://defi.palliora.org).

## What you can build

<table data-view="cards"><thead><tr><th data-type="content-ref"></th><th></th></tr></thead><tbody><tr><td><a href="/defi/build/quickstart.md">Quickstart</a></td><td>Create a shielded account, register, deposit, settle and withdraw with the SDK.</td></tr><tr><td><a href="/defi/build/sdk-reference.md">SDK reference</a></td><td>The packages, the <code>Core</code> class, the request types and the services you supply.</td></tr><tr><td><a href="/defi/build/integrate-a-protocol.md">Integrate a DeFi protocol</a></td><td>Write an adaptor so users can reach your protocol from a shielded balance.</td></tr><tr><td><a href="/defi/build/private-sub-accounts-sdk.md">Private Sub-accounts SDK</a></td><td>Derive Sub-accounts, fund them, buy return gas and bring the money back on HyperEVM.</td></tr><tr><td><a href="/defi/build/relayer-api.md">Relayer API</a></td><td>The HTTP interface of the HyperEVM relayer.</td></tr><tr><td><a href="/defi/build/troubleshooting.md">Troubleshooting</a></td><td>Errors from the SDK and the pool, and what causes them.</td></tr><tr><td><a href="/defi/build/for-agent-assisted-devs.md">For agent-assisted developers</a></td><td>Rules and entry points for coding agents working in this repo.</td></tr></tbody></table>

## How the pieces fit

| Piece              | What it is                                       | You use it to                                            |
| ------------------ | ------------------------------------------------ | -------------------------------------------------------- |
| SDK                | A set of TypeScript packages                     | Make keys, build, sign and prove transactions            |
| Pool               | A contract on Ethereum and on HyperEVM           | Register, accept deposits, check and record transactions |
| Verifiers          | Contracts that check proofs                      | Nothing directly. The pool calls them.                   |
| Adaptor            | A small contract between the pool and a protocol | Let a private transaction swap, lend or stake            |
| Bundler or relayer | A service that submits transactions              | Submit without exposing the user's wallet                |
| Data source        | An index of notes and tree leaves                | Find a user's notes and build Merkle paths               |

The SDK builds, signs and proves. It does not submit the transaction, and it does not ship a data source. You provide both. The [quickstart](/defi/build/quickstart.md) shows where each one plugs in.

## Two ways to submit

| Path    | Who submits                                     | What the public sees                 | Use it when                                        |
| ------- | ----------------------------------------------- | ------------------------------------ | -------------------------------------------------- |
| Wallet  | The user's own wallet calls `pool.transact`     | The user's wallet as the sender      | You test, or privacy of the sender does not matter |
| Relayed | A bundler on Ethereum, or a relayer on HyperEVM | The relayer or bundler as the sender | You want the sender hidden                         |

Deposits always use the wallet path, because the user's tokens move from their wallet. See [Relaying and gas](/defi/learn/concepts/relaying-and-gas.md) for how the fee works on each path.

## Before you start

* Read [How Palliora DeFi works](/defi/learn/how-it-works.md). It takes five minutes and the rest of this section assumes it.
* You need Node.js, a wallet key for a test network, and the pool address for that network. Addresses live in [Network reference](/defi/reference/network-reference.md).
* You need the circuit files (the `.wasm` and `.zkey` for each circuit). The prover loads them by path.

## Package names

The SDK packages are being renamed from `@veilnyx-sdk/*` to `@palliora.org/defi-*`. This section uses the new names. Until the rename ships, install the old names and change only the import paths. The mapping is in the [Rename map](/defi/reference/rename-map.md).

## Next

* [Quickstart](/defi/build/quickstart.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.palliora.org/defi/build/build.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.