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

# VI. Anatomy of the Void

#### **Smart Contracts (Rust, Solana BPF)**

* Accept deposit commitments and manage a Merkle tree of valid notes
* Validate zero-knowledge proofs during withdrawal
* Prevent reuse via nullifier tracking
* Token support includes SOL only at the moment with plans to expand additional tokens in the future.

**Zero-Knowledge Proof System**

* Uses zk-SNARKs to prove deposit ownership without revealing which one
* Compatible with Groth16/PLONK/Halo2
* Proof generation handled off-chain in client browser
* On-chain verifier accepts proofs to approve withdrawals

**Backend Indexer**

* Built with Node.js and GraphQL
* Ingests on-chain data (deposits, nullifiers, events)
* Stores indexed data in PostgreSQL
* Powers analytics dashboards and transaction tracking

**Frontend Interface**

* Built with React and `@solana/web3.js`
* Intuitive UI for depositing, withdrawing, and generating zk-proofs
* Connects to Solana wallets (Phantom)
* Responsive for both mobile and desktop


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://voidify.gitbook.io/whitepaper/vi.-anatomy-of-the-void.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.