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

# Privacy quality

Privacy isn't a switch, it's a crowd. This page is how to measure the crowd, how to stand in it properly, and what weakens it. Most protocols won't write this page. That's exactly why we do — a user who understands the crowd makes it stronger for everyone.

### The crowd is the product

When you exit the pool, an observer knows one thing: some entry became this exit. The question is how many entries it could plausibly have been. That count is the **anonymity set** — your crowd. Ten notes in your size: you're one of ten. Ten thousand: good luck. Every additional participant makes every existing participant harder to trace. Depth is a shared asset, which is why the whole protocol is tuned to grow it.

![FIG 4 · SAME NOTE, DIFFERENT CROWD, DIFFERENT PRIVACY](https://3506126944-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtlCeSg7ikIcaMHKqusLi%2Fuploads%2FQTFmaJRT2InAgbbNVbzy%2Ffig4-crowd.png?alt=media)

### Read the crowd before you join it

`pool_stats` publishes live depth per standard size. We put the number on the table so you can size the crowd before committing a wei — and so agents can make the same judgment programmatically. An agent that checks depth before entering is a well-built agent; the tool exists so that's one call.

### Standing in the crowd properly

* **Give it time.** Enter-and-exit in the same block is a signed confession — the two prints bracket you. Let other entries and exits land between yours. Time between prints is camouflage you get for free.
* **Don't mirror yourself.** Exiting the exact pattern you entered (three 10s in, three 10s out, same order, same hour) rebuilds the link you paid to break. Vary size combinations and timing.
* **Exit to fresh ground.** Settling out to a wallet already linked to you hands the observer the answer. Fresh address, or straight to a deposit address that was getting your funds anyway.
* **Mind the outside world.** The pool hides on-chain links. It can't hide you tweeting "just moved 100 ETH" at exit time. The tape isn't the only tape.

### What strengthens the crowd

Depth (more notes per size), churn (steady unrelated entries and exits), and uniformity (standard sizes doing their job). The roadmap is sequenced around exactly this — every feature that grows or thickens the crowd ships before features that don't. Machine flow helps too: agents entering and exiting around the clock are crowd, and they don't sleep.

### The honest ceiling

No system makes you untraceable against every adversary forever, and anyone who claims otherwise is selling something. What a deep pool plus good habits buys you: no public balance, no public counterparties, no public pattern, and an exit that could be any of thousands of entries. That's the product. Check the number, stand in the crowd properly, and it's a very strong product.


---

# 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://railhood.gitbook.io/railhood-docs/privacy-quality.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.