> For the complete documentation index, see [llms.txt](https://zaiffer.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zaiffer.gitbook.io/wiki/zaiffer/shielding-tokens-wrapping/automatic-wrapper-deployment.md).

# Automatic Wrapper Deployment

One of the most powerful features of the confidential token system is its **permissionless, self-expanding architecture**. Anyone can create a confidential version of any ERC-20 token without asking permission. When you shield a token for the first time:

**If a wrapper already exists**, the system simply uses the existing wrapper. You benefit from the shared infrastructure that someone else deployed.

**If no wrapper exists yet**, the protocol does not automatically [deploy a new wrapper](/wiki/zaiffer/deploying-new-wrappers.md)/cToken pair when the first user shields. However, a user can call the factory contract to deploy a new wrapper:

1. **DeploymentCoordinator** creates a new `RegulatedERC-7984Upgradeable` contract (the cToken)
2. Creates a new `WrapperUpgradeable` contract
3. Links them together (wrapper can mint/burn the cToken)
4. Adds them to the public registry
5. Charges a deployment fee (see Section X)

This means:

* **Permissionless expansion**: No whitelist, no governance vote required
* **Network effect**: Once deployed, everyone can use the same wrapper
* **Composability**: DeFi protocols can integrate any cToken
* **No central approval**: Truly decentralised privacy layer


---

# 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://zaiffer.gitbook.io/wiki/zaiffer/shielding-tokens-wrapping/automatic-wrapper-deployment.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.