> For the complete documentation index, see [llms.txt](https://void-protocol-2.gitbook.io/void-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://void-protocol-2.gitbook.io/void-protocol-docs/developers/sdk.md).

# SDK

## VOID SDK

The VOID SDK is the internal SDK used by the app to build private actions.

{% hint style="warning" %}
The SDK is **internal for now** and is not yet published as a public package.
{% endhint %}

### What It Handles

The SDK is responsible for:

* creating **notes**
* creating **commitments**
* encrypting notes to a receiver's key
* decrypting notes owned by the connected user
* building **Merkle witnesses** from indexer data
* preparing prover inputs for:
  * Shield
  * Transfer
  * Unshield
  * Trade (Private Buy, Sell and Swap)

The legacy Swap circuit is not used: its fixed-rate entry point in the pool is permanently disabled.

* encoding pool contract calls

### Proof Inputs

All proof inputs are built from:

* real private notes
* indexer data
* Merkle witnesses

{% hint style="info" %}
The SDK does not use placeholder note data for normal private actions.
{% endhint %}

### Public SDK

A public SDK for third-party applications is planned **after mainnet**.

The future public SDK is intended to make it easier for wallets, apps and other integrations to interact with VOID's private infrastructure.

{% hint style="warning" %}
SDK interfaces may change before public release.
{% endhint %}


---

# 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://void-protocol-2.gitbook.io/void-protocol-docs/developers/sdk.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.