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

# FAQ

#### **1️⃣ What is Sheriff.cash?**

Sheriff.cash is a **multi-chain privacy mixer** designed to **break blockchain surveillance** and ensure **fully anonymous** transactions.\
It operates on **Ethereum, BSC, and Solana**, using **a unique multi-layered mixing algorithm** that makes transactions **completely untraceable**.

***

#### **2️⃣ How does Sheriff.cash ensure privacy?**

Sheriff.cash uses a **proprietary transaction obfuscation mechanism** that involves:\
✅ **Randomized deposit splitting** into different amounts\
✅ **Intermediary wallet distribution with randomized delays**\
✅ **Exchange liquidity injection** to break on-chain traceability\
✅ **Final clean wallet payouts with no link to the original deposit**

Each mix follows a **unique pattern**, ensuring that no transaction can be backtracked by chain analysis firms.

***

#### **3️⃣ How much does mixing cost?**

Sheriff.cash charges a **0.7% mixing fee** per transaction.

* **All fees go towards $SHERIFF buybacks**, increasing token value.
* **Holders with $1000+ in $SHERIFF tokens** enjoy **free mixing**.

***

#### **4️⃣ How long does mixing take?**

The time required for mixing depends on **network congestion, randomized delays, and fund distribution**.\
On average, a mix **completes within 10-30 minutes**, but **randomized delays** are applied to improve security.

***

#### **5️⃣ Is there a minimum or maximum mixing amount?**

There is **no strict minimum or maximum**, but **larger transactions may require more time** for proper mixing.\
For **optimal privacy**, we recommend splitting large amounts into multiple transactions.

***

#### **6️⃣ Can I track my mix?**

No. Sheriff.cash does **not store or track** any user transactions.\
Once funds enter the mixing pool, they **cannot be linked back to the sender**.

However, you will receive a **Mix ID** that allows you to **check your transaction status** while it's being processed.

***

#### **7️⃣ Is Sheriff.cash decentralized?**

Yes. Sheriff.cash operates via **decentralized smart contracts** on Ethereum, BSC, and Solana.\
It does not **store user data** or require **KYC verification**, ensuring **full anonymity**.

***

#### **8️⃣ What makes Sheriff.cash different from other mixers?**

🚀 **Unique Mixing Model:** Unlike traditional mixers that use predictable "shuffling," Sheriff.cash **injects randomness** at every stage.\
🔗 **Exchange-Based Privacy:** By leveraging **high-liquidity exchanges**, Sheriff.cash ensures that **funds have no on-chain history**.\
🔥 **$SHERIFF Token Utility:** The **buyback model** rewards holders and strengthens the ecosystem.\
📡 **Resistant to Chain Analysis:** Unlike CoinJoin & Tornado Cash, **Sheriff.cash transactions cannot be clustered or linked**.

***

#### **9️⃣ Is Sheriff.cash legal?**

Privacy is a **fundamental right**. Sheriff.cash does **not facilitate illicit activities**—it simply provides users with a way to **protect their financial privacy**.\
Users are responsible for ensuring that their usage complies with local laws.


---

# 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://sheriff-cash.gitbook.io/sheriff.cash-docs/docs/faq.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.