> 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/standards-and-policy.md).

# Standards & policy

### Compliance without surveillance

Keep illicit funds out at the door. Give lawful users real privacy in between. Make clean provenance provable on the way out. That's the architecture — and policy is moving toward it, on the record.

### The receipts

March 2026: the U.S. Treasury tells Congress, in a report under the GENIUS Act, that lawful users may use privacy tools "to protect sensitive information on personal wealth, business payments or charitable donations from appearing on a public blockchain." Financial privacy, on the federal record. They wrote it about mixers; the point is bigger than mixers.

The 2023 U.S. national strategy made privacy-enhancing technologies — the exact family RAILHOOD's zero-knowledge design belongs to — a research and adoption priority. EU data-protection law runs on data minimisation: expose only what's necessary. Publishing every citizen's full financial history by default fails that test. Selective disclosure passes it.

### Where RAILHOOD maps

| Framework              | What it wants                                                          | RAILHOOD                                                                     |
| ---------------------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| NIST Privacy Framework | Control data exposure, enable disclosure choices, communicate clearly. | Off-market by default; viewing keys as user-directed disclosure; these docs. |
| PETs strategy          | Get utility from data without exposing it.                             | Zero-knowledge proofs: verify validity and provenance, reveal nothing else.  |
| Sanctions compliance   | Don't transact with sanctioned parties.                                | Screening at the door; clean-provenance receipts on exit.                    |
| Auditability           | Regulated entities must evidence their activity.                       | Viewing keys; exportable settlement receipts.                                |

One precision worth having: NIST publishes standards and frameworks — it doesn't certify DeFi protocols, for anyone. "Maps to the frameworks" is the strongest claim that exists, and the table above is RAILHOOD making it.

### The market-structure argument

Regulators have overseen confidential execution for decades — 40%+ of equity volume runs off-exchange inside a fully regulated system, because the rules distinguish *confidentiality from the market* from *concealment from the law*. Dark pools report to regulators; they just don't broadcast to competitors. RAILHOOD is built on the same distinction: private against the crowd, provable to the parties who have a right to ask. That's not a loophole; it's how mature markets already work.

### The direction of travel

Yes, privacy tech has had its court battles — sanctions fights, developer-liability debates, the lot. The law is in motion. But the destination is visible: not privacy *or* compliance, both. Viewing keys give honest users accountability on their own terms. Association sets — proving your funds aren't tied to known illicit sources without giving up privacy — are the research frontier we build toward. Tools that fight compliance get banned; surveillance rails get abandoned. RAILHOOD holds the middle, which is where the volume ends up.

Context, not legal advice — rules differ by jurisdiction. See [Disclaimers](/railhood-docs/disclaimers.md).


---

# 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/standards-and-policy.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.