Security
What this build does and does not do with keys, signatures and funds, plus production requirements.
The honest security summary of this build is short: there is nothing to steal. No keys, no signatures, no deployed contracts, no custody and no server-side account. That is worth stating precisely rather than reassuringly.
Current state
| Surface | State | Detail |
|---|---|---|
| Private key handling | None | No key material is read, stored or derived |
| Transaction signing | None | No signature is ever requested |
| Deployed contracts | None | No exchange contracts exist on any network |
| Contract addresses | Unset | Configuration values are undefined |
| Settlement | None | Balances are local arithmetic, not transfers |
| Custody of funds | None | There is nothing to custody |
| Server-side accounts | None | No backend, no account records |
| Audit | None | Nothing has been audited, and no badge claims otherwise |
What happens if you connect a browser wallet
- An injected provider is detected so the header can show that one exists.
- On an explicit click, the account list may be read to display an address. Nothing else is requested.
- No
eth_sendTransaction, nopersonal_sign, noeth_signTypedData, no chain switch. - The demo wallet is entirely local and is the only account that can place orders in this build.
Data handling
Balances, orders, fills, activity and interface preferences are stored in this browser under namespaced localStorage keys. There is no analytics pipeline collecting trading behaviour, no account to delete, and clearing site data removes everything.
What production would require
None of the following has been done. They are the conditions that would have to be met before real value could be at risk, listed so the gap between a prototype and a venue is explicit.
- Contract audits — independent review of the book, matching and settlement contracts, with findings published.
- Invariant and property testing — solvency, collateral accounting and queue integrity tested as invariants, not only as examples.
- Deployment verification — verified source for every deployed address, published in configuration the interface actually reads.
- RPC configuration — explicit endpoints, chain ID checks, and a refusal to submit anything when the connected network does not match Robinhood Chain.
- Transaction review — every action shown in full before signing: asset, size, price, limits and the contract being called.
- Operational limits — documented upgrade rights, pause conditions and who holds them.