> 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/execution-and-settlement.md).

# Execution & settlement

Getting off-market is easy. Getting back on-market without undoing the whole exercise is where the engineering lives. This page is the exit path, the fees, and the timing.

### The settlement agent

Here's the trap naive designs fall into: you exit to a fresh wallet, but that wallet has to pay gas — and funding it links it straight back to you. One transaction and the privacy you bought is gone.

RAILHOOD routes exits through a **settlement agent** (the relayer). It takes your proof, submits the exit transaction, and pays the gas itself, deducting a small cut from the amount. Your wallet never appears on the tape as the sender. Not once. The receiving address starts life with no visible past.

#### What the agent can and can't do

* It **can** submit your exit and collect its fee — that's the job.
* It **can't** steal, redirect, or alter your exit: the zero-knowledge proof pins the destination and amount, so a tampered submission simply fails on-chain.
* It **can't** see inside your history — it handles a proof, not your books.

### The full bill

| Line item            | Cost                                                   |
| -------------------- | ------------------------------------------------------ |
| Entry (protocol fee) | 0.25%                                                  |
| Exit (protocol fee)  | 0.25%                                                  |
| Settlement agent     | Small cut of the exit, in exchange for paying your gas |
| MCP tool calls       | Free                                                   |

That's everything. For scale: analysts peg the invisible markup from getting sandwiched on lit venues at a meaningful slice of every sizable trade — and that one repeats every time you show your hand. The off-market fee is paid once per round trip, on purpose, for a defined service.

### Timing and finality

Entries and exits confirm at Robinhood Chain block speed — this is on-chain settlement, not a batch window. The strategic timing question isn't the chain's, it's yours: exiting seconds after entering telegraphs the link between the two prints. Treat time in the pool as part of the trade. The full playbook is in [Privacy quality](/railhood-docs/privacy-quality.md).

### Settlement receipts

The roadmap's exit receipt is a zero-knowledge attestation: portable proof that your funds trace to screened, clean entries, produced without exposing a line of your history. Hand it to an exchange, a counterparty, an auditor — they verify the math, not your life. It's the clearing confirm of the off-market world: settlement finality plus provenance, minus the disclosure.

### Failure modes, plainly

* **Agent offline?** Your funds don't move without you — the note stays yours; exit resumes when a settlement agent does.
* **Chain congestion?** Exits queue like any transaction. Nothing about the wait leaks anything about you.
* **Lost note?** Bearer instrument rules: no note, no funds, no recovery desk. Back it up like a private key, because it is one.


---

# 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/execution-and-settlement.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.