01
External active identities
— weekly growth
Distinct participating identities across separate GitHub, wallet, and comment-author namespaces.
Public market evidence
Platform metrics
Participation, payout, and conversion from public GitHub activity and confirmed marketplace records.
Reporting period
Loading source-backed metrics…
02
Marketplace payout volume
— settled rounds in this period
Confirmed solver pay, verifier pay, and completion bonuses. Funding and refunds are excluded.
03
Mature claim-to-settlement
— mature claimed rounds
Recent claims stay outside the rate until they mature or reach a terminal event.
Repository acquisition · rolling 14 days
Thousands of repository actions
GitHub measures unique repository users separately as cloners and visitors. Their overlap is unknown, so these groups are not added together or to active platform identities.
loading
Loading GitHub's aggregate traffic window.
Repository clone operations. Repeat cloning can create multiple events.
Unique repository users measured by GitHub as cloners.
Views of repository pages during the same rolling window.
Unique repository users measured by GitHub as visitors.
1,260 clone events · 222 unique cloners · 98 views · 28 unique visitors 9 July public snapshot
2,448 clone events · 310 unique cloners · 280 views · 58 unique visitors 11 July public snapshot
Historical snapshots are overlapping rolling windows and are not summed.
Daily grain · UTC
Participation and payout trends
Identity counts are namespaced; payout is confirmed canonical USDC only.
Selected period
Who participated and who was paid
Role counts are not additive: one identity can perform several roles.
- Solver pay
- —
- Verifier pay
- —
- Completion bonuses
- —
Point in time
Current marketplace inventory
Current availability is separate from historical payout and conversion cohorts.
- Ready to earn
- —
- Exclusive claim
- —
- Open competitions
- —
- Verification ready
- —
- Standing meta-bounties
- —
- Currently funded
- —
- Solver rewards
- —
- Verifier rewards
- —
Inventory is loading.
Launch cohort
First month and lifetime
The first month is fixed: 8 July 2026, 20:22:19 UTC through 8 August 2026, 20:22:19 UTC.
MetricFirst monthLifetime
External active identities——
Marketplace payout——
Settled rounds——
Context, not participation
Acquisition and revenue
Browser analytics measure devices or browser profiles. They are not users and are never added to active identities.
First-party acquisition coverage begins after analytics deployment and has no historical backfill.
Monetization not active. Marketplace payout volume is not platform revenue.
Audit trail
Definitions and source coverage
Missing or stale required sources are marked partial or delayed instead of being presented as zero.
What is an external active identity?
One namespaced GitHub login, Base wallet, or normalized self-reported comment author with a qualifying action in the period. Namespaces are not merged, so this is participation—not verified unique people.
What counts as payout volume?
Solver reward, verifier reward, and timeout completion bonus from confirmed, block-time-verified BountySettled events across both live protocols, plus verifier pay from confirmed rejected-submission events.
What is a mature claimed round?
An exclusive-claim (network, bounty_id, round) whose deadline has passed or that already has a terminal canonical event. Immature claims are shown separately. Open Competition has no exclusive claim and stays outside this cohort.
How are repository users counted?
GitHub reports unique cloners and unique visitors for a rolling 14-day window. Both unique counts are shown as repository users, but GitHub does not expose their identities or overlap. They therefore remain separate and are not added to external active identities.
What is deliberately excluded?
Bots, maintainers in the public policy, browser visitors, stars, repository traffic from active platform identity totals, returned claim bonds, refunds, funding intentions, unconfirmed transactions, leaderboard prizes, and private operational analytics.
Only a confirmed canonical BountySettled event proves solver payment.