> 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/glossary.md). # Glossary Every term in these docs — the market words and the cryptography words, one or two sentences each. ### Market terms | Term | Meaning | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | The tape | The public record of transactions. In TradFi, the consolidated tape; here, the public ledger. Same word, same job. | | Off-market | Held or moved outside public view. In equities, 40%+ of volume executes off-exchange; RAILHOOD is the on-chain equivalent for balances and settlement. | | Market impact | The price moving against you because your order was visible. The reason off-market exists. | | Round lot / standard size | A standard trade unit. Uniform units make participants interchangeable — the foundation of crowd privacy. | | Upstairs market | Wall Street's historical name for trading negotiated away from the exchange floor. The instinct RAILHOOD inherits. | | Settlement agent | The relayer: submits your exit and pays the gas so your wallet never appears on the tape as the sender. | | Settlement receipt | The exit attestation — portable zero-knowledge proof your funds trace to clean, screened entries. | | Front-running / sandwiching | Bots trading around your visible order to extract value. The on-chain version of market impact, industrialized. | | Fair launch | Everyone gets access at the same time on the same terms. No presale. | | TGE | Token Generation Event — the moment the token goes live. | | Cliff | A period where an allocation is fully locked. Nothing moves until it ends. | | Linear vesting | After the cliff, tokens unlock in equal slices over time. A slope, not a dump. | ### Cryptography terms | Term | Meaning | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | The pool | A shared vault of sealed, encrypted notes — the off-market layer itself. The cryptography literature calls this design a shielded pool. | | Note | An encrypted record of value: "this much, owned by this key." A bearer instrument — a sealed envelope only your key opens. | | Commitment | The on-chain fingerprint of a note. Proves it exists without showing what's inside. | | Nullifier | The one-way stamp published when a note is spent. Kills double-spending without revealing which note died. | | Zero-knowledge proof | Prove a statement is true ("I own an unspent note") while revealing nothing else ("which one"). | | Anonymity set | The crowd your note hides in. Bigger crowd, stronger privacy. Published live via `pool_stats`. | | Viewing key | A read-only key. Holders see your activity; they can never move your funds. Books and records, on your terms. | | Clustering | Chain analysis that links addresses to each other — and usually to a person. | | MCP | Model Context Protocol — the open standard AI agents use to discover and call tools. | | x402 | An open standard letting software pay for an API call in stablecoins, instantly, no account. | --- # 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/glossary.md?ask=&goal= ``` `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.