Opaq, from prompt to receipt
Opaq reduces what an AI request exposes and lets you prove later what was asked and answered. These pages describe the code as it is today, including the parts that are planned and not built.
What Opaq is
Three parts run today, three are planned:
| Part | Status |
|---|---|
| Private request | Live. The app at /app: masking in your browser, the side-by-side view of what leaves, the answer and the receipt. |
| Masking | Live. 9 kinds of detail detected in your tab, including a word list you keep. |
| Proof and receipt layer | Live. The OpaqReceiptLedger records receipt hashes on mainnet; the verifier checks them. |
| Confidential compute | Planned. Models run inside trusted execution environments or a comparable technology, so even the provider cannot read the request in use. |
| Secure API gateway | Planned. A developer endpoint with the same masking and receipts. |
| Developer workspace | Planned. Usage dashboards and request management for teams. |
Why masking comes first
Most leaks through AI tools are not clever attacks. They are an email address in a pasted thread, an API key at the bottom of a log, a client's name in a draft. Once a request is sent, the provider holds it, and you rarely know how long it is kept or who reads it.
Opaq moves the decision to the only place you fully control: your own browser tab. Before anything is sent, the request is scanned, each sensitive detail is replaced by a placeholder, and you see the exact text that would leave. The answer can still refer to [EMAIL_1] or [NAME_2], and your screen fills those back in locally.
Masking is the part that works today with no special hardware. The stronger guarantee, keeping even the masked text unreadable while a model processes it, needs confidential compute, which is planned. The limits page draws that line in detail.
What Robinhood Chain is used for
- Recording receipt hashes, so a request and its answer can be proven unchanged later (ledger at 0x4B56f6f60B4EE467f10b9f840569213a62825ed4).
- Planned: paying for inference and API access, and permissions managed by contract.
- Never: storing prompts, answers or any text. The chain is public; only hashes go there.
- The AI computation itself always runs off-chain.
Questions
What is Opaq?
Opaq is a private AI request layer on Robinhood Chain. It masks emails, phone numbers, keys, wallet addresses and the names you list in your own browser before a prompt is sent, and turns each answer into a receipt you can anchor on chain and verify later.
How does Opaq work?
You type a request. Detectors in your tab replace sensitive details with placeholders such as [EMAIL_1], and you see side by side what stays and what leaves. Only the masked text is sent. The answer, the masked request, the model id, a random salt and your address are hashed into one receipt, which your wallet can record on the receipt ledger.
Is Opaq confidential computing?
Not yet. Today the masked text travels over HTTPS to a model provider, which can read it while it answers; without a provider, a demo function in your browser answers instead. Running models inside trusted hardware is planned and not part of this build.
What does a receipt prove?
That the texts in the receipt file existed together, unchanged, when the author's wallet recorded the hash. It does not prove which model ran, that the answer is correct, or what the provider did with the masked text.
Which network is Opaq on?
Robinhood Chain mainnet, chain id 4663, with ETH for gas. The wallet dialog adds the network to your wallet when you connect.
How do I buy $OPAQ?
$OPAQ is live on Robinhood Chain at 0x8eafc8d9f1d6e954b745f7a955ac1c3fec57a0bf. That address, shown on the token page and in the navigation bar, is the only one this site uses.
Do I need $OPAQ to use Opaq?
No. Private requests, receipts and the verifier are free. Token uses such as inference credits, API fees and feature access are planned and not live; nothing is promised about them.
What are the risks?
Pattern masking can miss details it has no rule for, so read the masked text before you send it. Anything you record on chain is public and permanent. A configured model provider sees the masked text. Contracts and code can contain mistakes; use small, non-critical requests first.