Session keys
Give your bot a key that can only do what you said.
Anyone running a bot today hands it their wallet key. Here you keep the wallet. You fund a small account of your own, and you hand the bot a session: which contract, which function, how much ETH per trade and in total, until when. Pause it or revoke it from your wallet in one transaction. Chit is not in the loop: no operator, no service, nothing of yours held.
- Your account
- —
- ETH in it
- —
- Status
- —
- Figures
Connect your wallet to see your account.
Fund it
ETH goes from your wallet to your account. Only your sessions can spend it, only within their rules; you take the rest back any time.
Tokens in this account. Only you can take them out.
A token not listed?
Grant a session
The bot's key is the address its process signs with. It pays its own gas; your account pays the trades.
Your sessions
Read from the chain, never from us. Pause holds a key; revoke ends it for good.
No sessions yet on this device. A session granted elsewhere shows up once you paste its key above and press Refresh.
Link to the bot
You came from Chit Bot. Create and fund your account above, grant the bot's key a session (its key and the beta's caps are filled in), then sign one message so the bot knows which account is yours. The bot never sees your key; the signature is the only proof it gets.
The bot's key: …. The message you sign names this chain, your account and a one-time code; it is good for 15 minutes.
Lead from this wallet
You came from Chit Bot to lead from the wallet you already trade with. No account, no session, no key handed over: connect that wallet and sign one message. From then on every ETH buy it makes on the venue is read from the chain within a few minutes, posted to the leaders' feed with its hash, and mirrored into your followers' own session accounts, each inside the caps they set and behind orus's read. Your sells are never mirrored. Close leader in the bot stops it any time; the wallet's own trades are never touched.
For your bot
One call. The account executes it with its own ETH; the bot's key only signs.
account.execute(target, valueWei, calldata) // from the key you granted canExecute(key, target, selector, value) // ask first, it says why not
The SDK is src/fleet/session-keys.ts in the repo: the ABI, the encoders, and canExecute so a bot never pays gas for a refusal.