The terminal
Wallet, history and privacy
Your wallet is the account. There is no registration, no server-side profile and no copy of your research on anyone else's machine.
The wallet as account
Connecting establishes two things: an address to read balances for, and an identity to scope your research to. The terminal verifies you are on Robinhood Chain — chain id 4663 — and offers to switch networks if you are not, because signing on the wrong network is the one mistake that cannot be undone by a reload.
Reading is open, acting is gated
Nothing behind the wallet prompt hides content. Every price, chart, profile and audit renders for a visitor who has never connected. What a session buys is the right to act — to run the resolver, to size an order, to sign.
Where an action is unavailable the control says what is missing rather than sitting greyed out, and pressing it starts the fix. A disabled button a reader cannot reason about is the thing that design replaces.
Research history is bound to the address
Threads are addressed to a wallet, not to a browser. Connecting a different wallet swaps the entire history: the previous owner’s conversations are not visible, not searchable, and not carried into the new session.
| State | What history shows |
|---|---|
| Disconnected | Only threads created while disconnected. |
| Wallet A connected | Only wallet A's threads. |
| Switched to wallet B | Only wallet B's threads. Wallet A's are retained, not shown. |
Deleting
- A thread can be deleted from the rail or from the History page. Because the action is immediate and irreversible, it asks first — naming the thread it is about to remove.
- Clear all threads on the profile page removes every conversation for the connected wallet, and says how many that is before it does.
- Both confirmations put focus on Cancel, so a reflexive keypress chooses the safe option.
What leaves your device
A question you send reaches the resolver, along with the connected address so the holder check can run. Market data is fetched server-side and proxied, so upstream providers never see your address and never receive a request from your browser. Nothing else is transmitted: no analytics on your positions, no export of your history, no server-side profile to breach.