Private funding for wallet fleets. Fund 30 wallets from one wallet, and a bubble map ties them to you. Chit funds the fleet instead: the chain shows a deposit into Chit and fleets funded by Chit, and no transaction links the two. Private, not anonymous. Your keys stay yours.
Read moreBuild Momentum 55How it is measured
Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.
Evidence: ship record
A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.
Follow puts Chit on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
Or read its RSS feed.
It compares building with market attention; it is not a prediction and not a reason to trade.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
2.81% HoodLock2.81% of the token supply is locked at HoodLock; the next 2.6% unlocks on 1 Dec 2026, and the last on 13 Dec 2026. Context HEY read from the locker, not a verdict.HEY can answer 17 of the 19 research questions that apply · Research coverage
Checked
Code activitySource linked
What changed, in the repository’s own words:
2 active days in ajanaku1/chit-app.
This week HEY looked inside 2 of 7 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
Record ship:bce41f39… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
Run a fleet of wallets, and you have a problem. Fund them all from one main wallet, and any bubble map ties the whole set back to you. Chit funds the fleet instead, so that link never gets drawn. Your main wallet deposits into a shared pool in one of three fixed sizes. Your fleet draws from the pool after a random wait of one to fifteen minutes. Gas is covered. The chain shows a deposit into Chit and fleets funded by Chit, and nothing connects them. Every limit is enforced by the pool contract and refused before any ETH moves: fixed deposit sizes, small draw caps, and an exit you can take yourself after 24 hours if we don't pay out, even with the service offline. Private, not anonymous. Your trades still show, and so do amounts and timing. Only the funding relationship is withheld, and Chit's operator can still see it. We would rather say so than let you find out. What's live today: the pool on Robinhood Chain testnet, the app at chit.tools, a Telegram bot as a testnet playground, and an ownerless buyback contract that burns CHIT hourly, with every event on chit.tools/burn.
Code activitySource linked
What changed, in the repository’s own words:
1 active day in ajanaku1/chit-app.
This week HEY looked inside 3 commits to see what changed: 1 changed code, 2 documentation or maintenance only.
Code activitySource linked
What changed, in the repository’s own words:
6 active days in ajanaku1/chit-app.
This week HEY looked inside 3 of 37 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.
Code activitySource linked
What changed, in the repository’s own words:
6 active days in ajanaku1/chit-app.
This week HEY looked inside 4 of 37 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.
Code activitySource linked
What changed, in the repository’s own words:
6 active days in ajanaku1/chit-app.
This week HEY looked inside 3 of 82 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.
Code activitySource linked
What changed, in the repository’s own words:
at least 3 active days in ajanaku1/chit-app since 2026-09-15; the count stops at the newest 100 commits listed.
Mostly maintenance or automation — not counted as building. A burst of 313 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 18 of 313 commits to see what changed: 18 documentation or maintenance only. 1 automated commit (bot accounts or a repeating scripted message) not counted.
Product launchHEY verified
Chit now has an ownerless buyback contract and a public page at chit.tools/burn that reads it directly 10% of fleet fees, plus one point per $100k of market cap, is sent into the contract daily. Once an hour, it spends 1% of its balance on the CHIT/ETH v4 pool and burns what it buys in the same transaction. No withdrawal function; immutable parameters; anyone can call it. The page shows total CHIT burned, ETH in and spent, the next buy, and every event with its explorer link.
Code activitySource linked
1 active day in ajanaku1/chit.
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.
Code activitySource linked
3 active days in ajanaku1/chit.
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.
Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.
Know something about Chit? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.
16 changes on HEY’s record for Chit: 1 release · 1 verification change · 1 contract in use again or for the first time · 1 token verification change · 12 other changes in 4 more kinds.
Code changes this week (since Mon 19 Oct) · 7 commits
Code changes, week of 2026-10-12 – 2026-10-18 · 3 commits
Code changes, week of 2026-10-05 – 2026-10-11 · 37 commits
Code changes, week of 2026-09-28 – 2026-10-04 · 37 commits
Trading was 170 trades a day in the seven days to 2026-09-28, down from 2,068 a day at its peak in the seven days to 2026-08-30 (29 days earlier), in HEY's decoded on-chain trades.
The full change record holds 8 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)
HEY can answer 17 of the 19 research questions that apply.
Not applicable here: Package advisories, Protocol economics.
A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
Observed after, 19–22 Oct so far: price −3.5% (before: −36.9%) · calls 217/day (before: 590/day) · volume $2K/day (before: $5.3K/day).
The latest ship, in the week of 19 Oct (week precision) — the week is in progress, 19–22 Oct so far, is too recent to compare: the days after it have not begun. This is the newest ship whose days after HEY has observed.
Code changes, week of 2026-10-12 – 2026-10-18 · 3 commitsCode activityin the week of 12 Oct (week precision)
| Measure | Observed before5–11 Oct | Observed after19–22 Oct so far |
|---|---|---|
| PriceAround this event:down 23.5 percent over 7 days· 11 Oct–18 Oct closes | down 36.9 percent over 7 days | down 3.5 percent over 4 days18 Oct–22 Oct closes so far |
| Volume per day | $5.3K/day | $2K/day4 of 7 days so fardown 61.9 percent against the days beforevs beforeagainst before |
| Liquidity | $25.2K | $21Kat 22 Oct so fardown 16.7 percent against the days beforevs beforeagainst before |
| Valuation | $70.9K | $52.3Kat 22 Oct so fardown 26.2 percent against the days beforevs beforeagainst before |
| Calls per day | 590/day | 217/day4 of 7 days so far−63.2%vs beforeagainst before |
| Calls to own functions per day | 2.6 | 0.54 of 7 days so far−80.6%vs beforeagainst before |
| Active contracts (busiest day) | 1 | 14 of 7 days so far |
| Distinct caller addresses (busiest day) | 49 | 704 of 7 days so far+42.9%vs beforeagainst before |
Observed around the same time — HEY does not claim this event caused it.
Market context and product usage, placed by time. Seven days either side; the day in progress is never compared. Open evidenceAs data
Chit’s code names the token of 1 published project.
Named in code or runs on a hook, read from public code and the chain: a link, never a partnership or an on-chain interaction. A code link is a reference: the code names the token, which shows neither a dependency nor use; only a hook link is a pool running on the other’s hook. As data
Posts by @usechit, as HEY last read them. Context only: a post is never counted as building and never sets the activity status.
Showing 5 of 17, newest first; HEY keeps 90 days.
