> For the complete documentation index, see [llms.txt](https://theduck.gitbook.io/quack-token-or-usdtheduck/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://theduck.gitbook.io/quack-token-or-usdtheduck/in-depth/proxy-wallets.md).

# Proxy Wallets

<figure><img src="/files/N88K5k9ZZMCE2juzDXuq" alt=""><figcaption></figcaption></figure>

## By utilizing Proxy wallets, a novel safety protocol is established, countering the traditional notion of "What's in your wallet."

The crucial aspect to note is that you never directly possess your tokens. Instead, the contract grants each supporter a modern method of holding through the Proxy wallet rights. This ownership exists on-chain, but Etherscan never tracks the specific holdings of your wallet. Consequently, a genuine connection is established solely between you and the contract, eliminating the need for transparency. It is important to emphasize that you do not physically possess $TheDuck; rather, the Free Proxy wallet securely holds it on your behalf.

Furthermore, this approach significantly complicates the tracking of tokens. With each purchase, the tokens are transferred to a newly created proxy wallet, effectively dissociating them from your previous holdings. This adds an additional layer of obscurity, making it challenging to trace the movement of tokens.\
\
The permit system verifies approval based on your wallet, and since you don't possess the token, you are unable to approve it on your wallet. This design is intentional and not a flaw, as it enhances the security of your tokens in case the permit system is exploited. Additionally, this approach aligns with the overall concept, ensuring that you maintain a clean record with the government, as you don't hold the token and cannot approve it on your wallet.

If your browser employs the permit system, the token code acts as a preventive measure, safeguarding you from potential future problems and preventing its usage.

### To resolve this issue, you can utilize Etherscan to initiate a sale.

{% content-ref url="/pages/uMG92NhL4pN266zKKfdy" %}
[Buy $TheDuck](/quack-token-or-usdtheduck/guides/buy-usdtheduck.md)
{% endcontent-ref %}

{% content-ref url="/pages/DlrPwLN9uw8FQYj3yKQq" %}
[How To Sell via Etherscan](/quack-token-or-usdtheduck/guides/how-to-sell-via-etherscan.md)
{% endcontent-ref %}

{% content-ref url="/pages/9XYnSQdjaAcAyuYM6x4o" %}
[How To Use your Proxy Wallets](/quack-token-or-usdtheduck/guides/how-to-use-your-proxy-wallets.md)
{% endcontent-ref %}

Due to our lack of trust in their permit system, we decided not to allow its usage within the proxy system and chose to opt out.

The router automatically grants approval when a transaction involves selling, but the inclusion of a permit system over the router is considered poor practice, and we actively avoid using it.

<figure><img src="/files/B41GMNztA3hqMxmk8nHz" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://theduck.gitbook.io/quack-token-or-usdtheduck/in-depth/proxy-wallets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.