Core · Core Secure
token 0x69a72eb9b313a516c02d42a0bb139b27c3d6682d
curve 0xb8d157637169cc8cec045a6e9731378d3843223a
| Launched | · block 74072395 · tx 0x1694…792c |
|---|---|
| Launchpad | pons v2 on Robinhood Chain (chain 4663) |
| Quote asset | ETH (native) |
| Creator tax | 0 bps (0%), on every buy and sell |
| Trade fee | 100 bps (1%), on every buy and sell |
| Deployer | 0xe015…cf48 |
Verdict: caution
No avoid rule fired, but one wallet holds 85% of the tokens bought on the curve (9 holders); 179 min after launch the curve has not graduated and its price is 10% of its peak (1.00x the launch price now, 10.52x at the peak).
top1_concentrated; base rate: at 3 s, 82% of ETH launches 2026-09-19..25 with a holder snapshot had a top holder at 50% or more, and 0.89% of those graduated against 2.84% of the rest (n=22,947 / 5,042))collapsed_not_graduated; base rate: of launches not graduated 30 min after launch (2026-09-06..26, n=375,631), 0.31% graduated later)As of 2026-09-27 19:12:02 UTC. The rule, its thresholds and the base rates it rests on are public at /v1/labels (rhc_verdict); it is not odds, not a prediction for this curve and not a safety verdict. The paid curve card gives the verdict at request time with the deployer record and an exact sell check.
| Outcome | not graduated when we last read the curve (2026-09-27 19:12:02 UTC); last curve trade observed 2026-09-27 17:08:33 UTC |
|---|---|
| Raised at the last state | 0.0011 ETH of the 4.2 ETH graduation raise (0.0%) |
| Peak raised | 89.8% of the graduation raise |
| Price vs launch (exact curve model) | 1.00x at the last state, 10.52x at the peak |
| Curve trades observed | 389 buys, 238 sells |
A pons curve graduates when its real quote reserve reaches the graduation raise (4.2 ETH on ETH-quoted curves): the curve completes and a pool opens. Raised and price come from the exact constant-product model rebuilt from the curve's own buy, sell and fee-sweep events (fee and creator tax on both legs). From our own independent capture of public pons v2 factory and curve events on Robinhood Chain (chain 4663), not resold data.
| measure | at 3 s after launch | latest snapshot (2026-09-27 19:12:02 UTC) |
|---|---|---|
| Holders on the curve | 1 | 9 |
| Top holder share | 100.0% | 85.0% |
| Top 5 holders share | 100.0% | 99.9% |
| Deployer holding share | 0.0% | 0.0% |
| Same-block direct-buy cluster share | 0.0% | 10.2% |
| Wallets in same-block direct-buy clusters | 0 | 16 |
| Buys sent direct to the curve | 0.0% | 88.7% |
| Buys through a terminal router | 100.0% | 11.3% |
| Held by terminal-router buyers | 100.0% | 86.4% |
| Unique buyers | 1 | 90 |
| Buys tied to a sender | 0.0% | 99.0% |
Holders are wallets with a positive balance bought on the curve (pool trades after graduation are not counted). A same-block direct-buy cluster is a set of wallets that bought directly from the curve in one 100 ms block with at least one other direct buy; matching timing does not establish coordination or common ownership, and on pons v2 such a cluster is often the launch team's own opening bundle, bought by addresses the launch call exempted from the snipe tax. A terminal router is a trading front end's contract; routing does not identify a human or a bot.
The ring rule published with our paid cards: unique_buyers >= 8 and structure.same_block_direct_cluster_share >= 0.5, that is at least 8 buyers 3 s after launch and the wallets buying direct from the curve in the same 100 ms blocks (a block with at least 2 direct buys) holding at least 50% of the tokens bought.
Here at 3 s: 0 wallets buying direct from the curve in the same 100 ms blocks held 0.0% of the tokens, with 1 buyers in all.
This launch at 3 s: does not match. On the latest snapshot: does not match.
When a launch matched this rule at 3 s (at least 8 buyers, and the wallets buying direct from the curve in the same 100 ms blocks holding at least 50% of the tokens), 92.7% of such launches did not graduate and those ended near 0.36 of their peak price (ETH launches of 2026-09-19..25 with a 3 s snapshot, n=28,147); on pons v2 such a cluster is often the team's own opening bundle, which the launch call can exempt from the snipe tax. Base rates over other launches, not odds for this curve.
Why the team's own bundle: the pons v2 docs describe a launch call that exempts up to 32 addresses from the snipe tax "for a team bundling its opening buys across several wallets", and in 63% of the 2,176 launches that matched at 3 s in 2026-09-20..27 most of the cluster's buying in seconds 0-2 paid no snipe tax (measured 2026-09-27 on our tape).
The 09-07 study is our own pons v2 capture of 2026-09-06/07 with the structure read 3 s after launch: 14.5% of launches matched the rule, 47% of the ETH launches matching it fell to 0.6x of their price or less within 60 s (dumped), and their median ended at 0.37x its launch price. Matching timing does not establish coordination, common ownership or intent.
Open on pons · explorer · DexScreener (free redirects through this site to third-party pages, no referral code and no fee; not a recommendation to trade)
Free: Robinhood Chain launch data · pons statistics · label rules · this record as JSON. Pay with USDC by x402 or a prepaid key; prices at /pricing.