Launch app

@usechit_bot

Trade the chain
from Telegram.
Keys and all.

Your keys
The bot trades from an account you own, inside a session you set and pull back in one transaction.
Three readings
Orus on safety and Hey Research Lab on the builder, on every token before you buy. Eyebrow on our own toolchain.
Orders
Limit buys and DCA that fire on your session while you sleep.
Proof
Tap 📸 and a position becomes a picture: what you paid, what the pool would fill, your link on it.

Chit Bot

bot

Today

0xd523a627030509021cc39b6d7c8543417d3e50d812:04 ✓✓

$CHIT · 0xd523…50d8

Price 10,738,347 per ETH · pool 9.53 ETH

Orus: Honeypot unknown · bundled 29% · top 10 hold 25% · 502 holders

Hey Research Lab: Shipping · 204 commits · verified builder

Eyebrow: Toolchain locked and signed, clean

Your account holds 18.4M CHIT

Buy 0.01Buy 0.05Buy 0.1
Limit buyDCA
Sell 25%Sell 100%
📸 Share↻ Refresh

The card

Paste a contract.
The rest is a button.

01 / 10

Buy

Your three presets or a custom amount. Quoted from the pool with fee and price impact, guarded by your slippage setting, sent through the real Uniswap v4 router. The reply carries the hash.

Buy 0.01 · 0.05 · 0.1

Robinhood Chain · 4663

0x7a3e…c914 (tap to copy)

Balance: 0.42 ETH · 18.4M CHIT

Every figure is read from the chain when the card is drawn. Tap a key to hold it.

Before you buy

Three readings
on the card.

Asked alongside the chain reads, so a card never waits on a partner alone. Each line links back to its source.

Orus

Safety, on every token

  • Honeypot
  • Taxes
  • Bundlers
  • Top 10 share
  • Holders
  • Liquidity, and whether the LP is burned
  • The deployer's launches

A blank from Orus reads as unknown, never as safe.

Hey Research Lab

The builder, on every token

  • Status: shipping or still building
  • Commits in the last 30 days
  • Releases in the last 30 days
  • Verified builder

A missing field is skipped: unknown, never zero.

Eyebrow

Our own toolchain, on the $CHIT card

  • Chit is written with AI coding agents
  • Their skills, servers, hooks and rules, in a signed lockfile
  • Checked on every push and every deploy

A drift is said as plainly as a clean result.

A key with a ceiling

Other bots take your key.
Chit gives you speed without it.

  1. 01

    Create my account

    One per wallet, its address known before it exists. One transaction.

  2. 02

    Fund it

    ETH from your wallet to the account. Take it back any time.

  3. 03

    Grant a session

    The bot's key, the router it may call, how much per trade, how much in all, until when.

  4. 04

    Watch it

    Every session shows its spend, its calls and its state, read from the chain.

  5. 05

    Pause, resume, revoke

    Pause holds the key, revoke ends it for good. One transaction from your wallet.

Session key

@usechit_bot · 0x91c4…7e20

Active

Per trade

0.05 ETH

The most one call can spend: a tenth of the total

Spent

0.12 / 0.5 ETH

Every trade counts against it, and the key stops at the top

Time left

4 d 6 h of 7 d

Then the key is dead, whatever is left

May call

Universal Router

Let it sell

Off until you switch it on

PauseRevoke in 1 tx

An example key. The figures are the beta's defaults, and every one is set per key by you on the Sessions page.

Under the buttons

Built so a tap
moves money once.

01

Read, not remembered

Every figure on a card is read from the chain when the card is drawn.

02

A real transaction

Every trade is sent on chain, and the reply carries its hash.

03

Never sent twice

A trade with no receipt in forty seconds is reported as still landing, with its hash, and the bot refuses to send it again.

04

One lock per wallet

Two taps, or one tap delivered twice, cannot race on a nonce or spend twice.

05

No fee in the contract

The session account has no Chit address in it and no operator. Its rules are on chain for anyone to read.

06

Proven on a fork

A bot buys through its session, is refused outside it, is revoked, and the owner takes everything back.