Security model
How SLEEP keeps your funds yours: a smart account you own, limits enforced onchain, checks before you sign, and an executor key that never leaves secure storage.
What SLEEP can’t do
- Withdraw your tokens or send them to any other address.
- Trade tokens, amounts or prices you didn’t sign for.
- Accept a price more than 15% worse than the reference, whatever a rule says.
- Charge more than your signed fee cap.
- Keep acting after the expiry you signed, or after you close the position.
Limits enforced onchain
SLEEP’s policy contract runs every trade through your signed limits: the allowed tokens and approved Uniswap routes, the per-trade, total and rolling caps, the validity window, the price floor against an independent reference, the fee caps and a USDG depeg check. Each trade also carries a one-time execution key, so the same trade can never run twice.
Checked before you sign
Before your wallet opens, the SLEEP app decodes every call it is about to ask you to sign and checks it against contract addresses built into the app: the right chain, the right contracts, price feeds SLEEP trusts, and limits within its bounds. If anything doesn’t match, it refuses to continue, even if SLEEP’s own servers asked for it.
Keys
SLEEP never sees your wallet’s keys. Its executor key, the one that sends automated trades, is kept in secure server-side storage and never appears in code, logs or the website. Even with that key, an attacker could only make trades inside users’ signed limits.