Where your keys live
What CHEZ can and cannot touch, the limits this server runs with right now, and checks you can run in this browser.
The path a key takes
- 01
Your accountPrivy log-in
Email or a wallet, through Privy. It holds your log-in and settings; it holds no key.
- 02
Trading walletPrivy embedded wallet
Made for you at log-in. Its key lives in Privy’s secure enclave. CHEZ never sees, stores or sends a private key.
- 03
Orders signerOnly if you allow it
Tap Allow orders and CHEZ’s signer may buy on a listed curve up to the per-trade cap, sell, and approve that curve. Nothing else, on chain 4663 only. Revoke takes it off.
- 04
The chainRobinhood Chain
A signed transaction goes to the chain’s own RPC and lands in a block anyone can check on the explorer.
Limits on this server now
Reading the limits…
The caps bind orders the server runs for you (limit, DCA, take profit, stop loss). A trade you tap yourself is signed for that one trade.
What CHEZ checks before a trade
- Every trade is simulated first, and the least you accept is set from your slippage (orders: 25% at most).
- A curve joins the allowed list only after CHEZ checks it against the curves the Pons factory launched.
- A live order needs a fresh Privy access token (under an hour old) for a wallet you own; a session cookie alone cannot spend.
- A pending row is written before signing, so a crash can neither lose nor repeat a trade; the network fee is capped.
- An order stops after 3 reverts in a row.
- A transfer out of a trading wallet always shows Privy’s own confirm screen.
The risk that remains
Whoever controls the CHEZ server’s Privy secrets could add a contract of their own to the allowed list and send buys to it, up to the per-trade cap each time. The caps bound that loss per trade, and you can tap Revoke on any trading wallet to take the orders signer off at once. Trades you tap yourself do not depend on that signer.
Checks you can run here
- The page is served over HTTPSNot run yet
- A Content Security Policy guards the pageNot run yet
- Robinhood Chain answers as chain 4663Not run yet