> For the complete documentation index, see [llms.txt](https://docs.nullmask.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullmask.pro/introduction/what-is-nullmask.md).

# What is Nullmask?

Nullmask is a novel on-chain privacy architecture that enables users to transact privately from any existing multichain wallet. It requires no new wallets, seeds, backups, or special addresses — just a one-time setup that takes less than 20 seconds.

### The Virtual Network Approach&#xD; <a href="#the-virtual-network-approach" id="the-virtual-network-approach"></a>

Instead of depending on wallets to implement new privacy features or requiring users to migrate to new wallets, Nullmask integrates seamlessly into any existing multichain wallet as a new **virtual network**.

This network is not a real network like Arbitrum; it is a mechanism that inserts a custom RPC proxy service between a wallet and a full RPC node. This proxy shields outgoing transactions and decrypts incoming transactions for wallet accounts. It can run either on a remote server or in the background on a user's device (mobile app, browser extension).

### Why Nullmask?&#xD;

Current privacy solutions require users to:

* Install dedicated wallets with new seed phrases (Railgun, Zcash)
* Manage per-deposit note secrets (Tornado Cash)
* Re-enter seed phrases on every visit (Privacy Pools)

Nullmask eliminates all of these requirements. Users simply add the Nullmask virtual network to their existing wallet and transact as usual. The protocol handles everything else transparently.<br>

### How is this possible?&#xD;

Nullmask leverages recent breakthroughs in zk-SNARKs. Specifically, the UltraHonk prover enables proving the integrity of an EIP-1559 transaction and verifying its ECDSA signature on a consumer-grade device in approximately two seconds.

This means:

1. The user signs a standard EIP-1559 transaction in their wallet
2. The proxy intercepts the signed transaction
3. A ZK circuit proves the transaction is valid without revealing its contents
4. A relayer submits the proof on-chain, hiding the sender's identity
5. The smart contract verifies the proof and updates the privacy pool

The spending authority **never leaves the wallet**, making Nullmask more resilient to phishing attacks and fully compatible with hardware wallets.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nullmask.pro/introduction/what-is-nullmask.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 `build a script that syncs our docs to a CMS` 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.