Chit
Launch app
CHIT token 0xD523A627030509021cC39B6d7C8543417D3E50D8

Private funding pool live on testnet 46630

A private line for a public fleet.

Your main wallet never funds your fleet. The chain shows a deposit into Chit and fleets funded by Chit, and no transaction links the two. Trades stay public, and so do amounts and timing; only the funding relationship is withheld, and Chit can still see it.

Open the app

Live on Robinhood Chain testnet with test ETH. Next: a capped beta on mainnet for CHIT holders, not audited by a firm yet, with the caps kept until it is.

Runs on

  • ERC-4337 EntryPoint v0.7
  • Uniswap v4 Universal Router
  • Robinhood Chain testnet 46630
  • viem
  • Vercel

Chit is independent and not affiliated with, sponsored by, or endorsed by Robinhood, Uniswap, or any other project named here.

Fleet policy

0.2

/

0.5

draw

balance

Caps enforced on chain

Refused before any ETH moves

Deposit confirmed

funding delay 1–15 min

exit opens after 24 h

Chit balance

0.0500 ETH

▲ 0.05

Deposits carry no campaign key

The chain shows a deposit into Chit, and fleets funded by Chit.

Bounded by  not by promise

Every limit below is enforced by the pool contract on Robinhood Chain
testnet 46630, and refused before any ETH moves. Chit's operator can
still link a deposit to a fleet. Private, not anonymous.

Funding Delay
Deposit to fleet

min

Maximum wait
before funding

Draw Cap
Per campaign

ETH

Refused on chain
above this

Self-Serve Exit
Recovery without Chit

h

Works with the
service offline

01 / 03Funding delay

Your fleet is funded on a timer, and the contract sets the floor under it.

minat most, never under 1

Enforced by

  • MIN_FUNDING_DELAY = 60the shortest legal wait, in seconds
  • openDraw → DelayTooShorta draw due sooner than 60 s is refused
  • fund → NotDuenothing seeds a fleet before its due time

Why it exists

A deposit into Chit and a fleet funded by Chit are both public. If they landed a block apart, anyone could pair them by time. The wait is random, between one and fifteen minutes, so the timing tells an observer less; while the pool is small it can still tell them something. Deposits come in three fixed sizes (0.01, 0.05 and 0.1 ETH) for the same reason: one looks like any other of its size.

Still true

The one-minute floor is the contract's. The fifteen-minute ceiling is Chit's service choosing a wait; the chain would accept a longer one, never a shorter one. Chit's operator knows which deposit a draw belongs to. The wait hides that from the public, not from Chit.

02 / 03Draw cap

No campaign can pull more than 0.2 ETH from the pool, whatever the operator asks for.

ETHper campaign

Enforced by

  • DRAW_CAP = 0.2 etherthe most any one campaign can claim
  • openDraw / topUpDraw → DrawCapExceededabove the cap, a draw neither opens nor grows
  • fundPrincipal → DrawExceededa buy that would overspend the draw is refused before principal moves

Why it exists

The pool is shared, so the damage any one campaign can do has to be bounded by code, not by policy. Principal moves one buy at a time, just before that buy. Unspent draw never leaves the pool, and a failed buy is rolled back and charged nothing. A depositor holds at most 0.5 ETH in the pool, and the pool itself is capped at 5 ETH.

Still true

The cap is per campaign, not per operator. The operator can open more than one draw, up to what the pool holds and its 5 ETH cap allows. The cap bounds how much a mistake, or a compromised operator key, can move in one go. It does not make the operator trustless.

03 / 03Self-serve exit

You take your unspent balance back with two transactions Chit never has to sign.

hafter the request

Enforced by

  • EXIT_DELAY = 24 hoursexecuteExit reverts ExitNotDue before then
  • requestExit / executeExitcallable by the depositor alone, no operator role, and neither checks paused
  • POST_WINDOW = 12 hoursa charge not posted within 12 h of queuing expires unposted

Why it exists

If Chit goes offline, is paused, or disappears, your deposit is still yours to recover from the contract directly. The 24-hour wait lets every charge that is genuinely yours land first: the operator has 12 hours to post a queued spend, so by the time the exit pays there is nothing left to post. Anything unposted after that is Chit's loss, not yours.

Still true

The exit pays what is unspent at execution, not what was unspent at the request, so exiting is never a way out of a bill already due. The wait is a full day. It cannot be shortened, by you or by Chit.