An unofficial, community-built view into Vibe/Vibe activity on Robinhood Chain Testnet.
SnapshotSeptember 26, 2026Block 124,399,779
Launches, transactions and actor addresses reconstructed from full-history onchain data. Transactions are counted by distinct hash; actor addresses are deduplicated globally across creator, buyer and seller roles.
Total launches
160,851
Full history across all three configured factories
Indexed transactions
3,431,107
Unique tx hashes across full-history launch and curve activity
Indexed actor addresses
118,251
Distinct creator, buyer and seller addresses across indexed launch and curve activity
Current generation
101,143
Launches indexed from gen3, the current factory generation.
Factory generations
3
Three factory generations currently tracked by the indexer.
Indexed through block
124,399,779
Head block at the time of the validation run
The broader participant measure, overlapping categories and the exact event roles covered.
Indexed actor addresses are distinct creator, buyer and seller addresses observed across indexed Vibe/Vibe launch and curve activity. Addresses are globally deduplicated across all configured projects and event roles.
118,251
The broader union also includes Bought.recipient. It can differ from Bought.buyer, so receiving tokens alone does not make an address an actor.
Addresses can represent people, contracts or intermediaries. Event roles are not necessarily transaction senders, and address counts do not measure people. Valid contract addresses remain included; no identity enrichment or EOA/contract classification is performed.
Cumulative for configured factories and their known curves from block 95,916,239 through 124,399,779. Lifecycle initiators cannot be measured from the current event data. Post-graduation DEX activity and unconfigured factories remain outside this scope.
Category totals overlap and must not be added to produce a global count. Multi-project means more than one distinct factory-scoped launch identity. Repeated events and roles within one project count as one project for an address. Actor project membership uses creator, buyer and seller roles; participant membership also includes buy recipients.
Distinct normalized nonzero addresses in the global union of TokenLaunched/TokenLaunchedQuoted.creator, Bought.buyer and Sold.seller. Actor describes an event role, not a transaction sender or a person.
Distinct normalized nonzero addresses in the global union of actor addresses and Bought.recipient. A recipient may receive tokens without initiating activity. Each address counts once across all included roles and projects.
Trim whitespace, accept an optional case-insensitive 0x prefix, require exactly 40 hexadecimal characters, and lowercase before deduplication. Reject malformed and zero addresses with separate counters; do not filter valid contracts.
Preserve every valid nonzero address in an included role, including contract and intermediary addresses. Do not classify EOA versus contract. An infrastructure address counts if it independently appears in an included role.
Included actor roles: TokenLaunched.creator, TokenLaunchedQuoted.creator, Bought.buyer, Sold.seller. Additional participant role: Bought.recipient.
Excluded roles: TokenLaunched/TokenLaunchedQuoted.creatorFeeRecipient, TokenLaunched/TokenLaunchedQuoted.creatorVault, TokenLaunched/TokenLaunchedQuoted.token, TokenLaunched/TokenLaunchedQuoted.curve, TokenLaunchedQuoted.quoteCurrency, factory/log-emitter address, CreatorFeesForwarded.vault, LaunchFeesClaimed.treasury, other infrastructure/configuration addresses without an included event role. An address in an excluded role can still count if it independently appears in an included role.
Source run finished September 26, 2026 at 03:52 UTC. Aggregate derived September 26, 2026 at 03:56 UTC from the reconciled source data. The derivation date does not advance the source head. Full-history coverage and source counts passed validation, with 0 unusable address values and 0 unmapped trade events.
Three factory generations have produced launches on this testnet, and they are not evenly sized.
Retired and legacy are the operator's labels for these factory generations, not observations of whether a factory is active. Legacy and current were both still producing launches near the head block of this run. The retired one, which the operator no longer lists anywhere, was not: its most recent launch sits 723 blocks below the head. Its launches still count, which is why it is listed here at all.
Each generation is a separate factory with its own launch id counter, so a launch is only identifiable by generation and id together. Their trading economics differ, which means a single platform-wide fee rate would be wrong.
6 launches were added in the delta. The latest observed launch is 723 blocks below the pinned head. Operator labels do not determine inclusion.
1,682 launches were added in the delta. The latest observed launch is 189 blocks below the pinned head. Operator labels do not determine inclusion.
61,430 launches were added in the delta. The latest observed launch is 4 blocks below the pinned head. Operator labels do not determine inclusion.
Where the data came from and how fresh it is.
These figures come from an open source indexer that rebuilds every launch from chain logs, reading events straight from Robinhood Chain Testnet rather than from any operator API. That is why the numbers on this page can be checked against the chain instead of taken on trust.
Nothing here is live. Event counts are fixed at the head block shown above and stay fixed until a newer validated snapshot is connected. Fee models, graduation targets and address-book evidence retain their own verification dates. Advancing event history does not imply that this other metadata was read again.
Worth reading before quoting any number on this page.
No on-chain registry of factories was found, so the indexer works from a hand maintained list. Counts cover configured factories and their curves. Additional event-signature checks can find other emitters, but cannot establish complete discovery of every possible protocol deployment.
The transaction figure counts distinct transaction hashes on the launch and curve event surfaces this indexer reads. It is not every Vibe/Vibe transaction, and nothing here could establish that it was. What falls outside it is listed below.
Event counts were validated on September 26, 2026 through block 124,399,779. The chain continues moving. Separately verified metadata keeps its own evidence date.
Robinhood Chain testnet only. Values are test values and the testnet can reset. Community research, not an operator product.
What counts as a transaction: 3,431,107 distinct transaction hashes emitting TokenLaunched, TokenLaunchedQuoted, Bought, Sold, CurveCompleted, Graduated, CreatorFeesForwarded, from the earliest factory deployment through block 124,399,779. A transaction that emits several of those events counts once, so the per category figures shown under Indexer status do not add up to the total. Not counted:
Across full history the run saw 536 log events carrying a curve event signature from contracts outside the configured factories, from at least 97 distinct addresses. A shared event signature alone does not establish a Vibe/Vibe deployment. A fuller writeup lives in docs/known-limitations.md in the indexer repository, and a Known Limitations section is planned here.
The original 97,733-launch prefix through block 121,309,670 was reproduced unchanged. A contiguous delta covers 121,309,671–124,399,779. The operator configuration and pinned factory getters matched the configured factory and infrastructure addresses; its application deployment version changed. A topic-only launch-event scan of the complete delta found no unconfigured launch emitter. The delta excludes 34 curve-topic logs from 12 contracts outside the combined launch registry; the cumulative excluded total is 536 logs from 97 distinct contracts. September 18's separate review of 86 historical foreign contracts is retained as historical evidence; the new foreign emitters are excluded by project attribution and are not claimed to have undergone that bytecode review. No canonical registry establishes every possible factory, and different event signatures remain outside discovery. The last preserved historical event hash is at 121,309,669; the event-free old-head block 121,309,670 is inherited from the validated prefix. Canonical head hashes were checked before and after the delta scan; this is a pinned snapshot without a finality claim.