Skip to content
HEY Research Lab
Menu

BELL POOLS

$BELL

DEX

Contract 0xc5d6c1d90c8a87a07e2670b99b1556e818803228

HEY holds 225 other Robinhood Chain tokens with the ticker $BELL. This page is only the contract above. See them

Is this your project? Claim it →

Uniswap v4 hooks with Wall Street hours. LPs earn every session fee, 5 bps regular up to 100 bps closed. Protocol revenue: a flat 49 USDG per pool launch. No proxies, no blocked exits.

What HEY knows

Development

Shipped this weekShipping: 2 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 32How it is measured

Latest: Code changes this week (since Mon 9 Nov) · 29 commits

Token market · context

Launch pool only

Same ticker, different contract: 1 other published project uses the ticker $BELL. This page: its site bellstocks.tech names 0xc5d6…3228. Bellwether: its site bellwether.fun does not name 0xb38c…49eb. HEY does not say which is the real one — only what each project’s own sources name.

Token check

Project names this contract
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts BELL POOLS on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow BELL POOLS

No account? Email me BELL POOLS’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Attention
Discovery Gap not measured — market too thin. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 144 calls to the contracts' own functions in 7 days; the other 5,074 of 5,218 calls were ERC-20 token transfers and approvals, which trading alone produces.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact1 contract on record for code changes, 1 with published source code; latest change 8 days ago: Contract 0xc5d6…3228 source published on the explorer. Source
Not yet known
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-11-14.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 9 Nov) · 29 commitsCode changes, week of 2026-11-02 – 2026-11-08 · 112 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Project names this contract.
Project names this contract: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedProject names this contract: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Launch pool only.
Launch pool only: the only pool is the launch pool holding the token’s own supply, and it traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Launch pool only”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — market too thin.
Not measured — market too thin: the tracked token's market reads “Launch pool only”. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 16 of the 19 research questions that apply.
16 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 11d ago.

Building

  • Building activityMeasuredRead 17m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d ago.

Contracts

  • Contract creationMeasuredRead 15h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 21h ago.
  • Contract interfaceMeasuredRead 21h ago.

Market

  • Current marketMeasuredRead 1h ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 2d ago.
  • LocksMeasuredRead 6m ago.
  • Market checksMeasured

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.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 9 Nov) · 29 commits

Code activitySource-backed

What changed, in the repository’s own words:

4 active days in belldex/bell.

This week HEY looked inside 3 of 29 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.

Record ship:98e0f99c… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-11-14; HEY first knew on 2026-11-14.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

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.

View evidence ↗ (opens in a new tab)

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 10 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-11-02 – 2026-11-08 · 112 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in belldex/bell.

    How HEY read this week

    This week HEY looked inside 3 of 112 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.

    View evidence: Code changes, week of 2026-11-02 – 2026-11-08 · 112 commits (opens in a new tab)

Other changes on HEY’s record

8 changes on HEY’s record for BELL POOLS: 1 contract in use again or for the first time · 1 token check change · 1 new project on HEY · 1 contract change · 4 other changes in 2 more kinds.

All 8 changes for BELL POOLS →

The full change record holds 3 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0xc5D6C1D90C8a87a07E2670b99b1556E818803228 on Robinhood Chain

0xc5d6…32280xc5d6c1d90c8a87a07e2670b99b1556e818803228

Project names this contract.

Market context

Launch pool only · FDV (fully diluted) $12.1K · liquidity $9.1K (launch pool inventory, not a market) · reading 1 h old (GeckoTerminal).

Token

Launch stage
Trading in a DEX pool
Pair age
11d ago

Market

24h volume
$8.6K
The market status rests on $8.8K of trading volume HEY read within a day of this reading, from another reading or its record of on-chain trades — not on this reading’s own figure.
Trades 24h
55 buys · 45 sells
Price 24h
down 37.5 percent over 24 hours· 6hup 9.5 percent over 6 hours· 1hup 18.7 percent over 1 hour

The pool still holds the token’s own supply, so its reported liquidity is not a depth figure; trades in the last 24 hours are what make this a market.

Market history, trading and checks →

Market integrity

Liquidity is 33% below the level it held two days running ($12.2K, 2026-11-08).

Market
Launch pool only
Last day with trading
2026-11-14

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-15 12:55 UTC · How HEY checks this

Sources

4 places HEY reads for BELL POOLS