60,000 participants completed a five-contract builder track.

The supplied case study was reconciled with both campaign configurations and their participant exports. Public figures are rounded. Completion records establish campaign status; they do not independently establish unique people, original code or ownership of every submitted deployment.

Cohort and observation window

The main export contains 127,543 distinct participant IDs; 104,485 have at least one completed task. Completion history runs from July 17 to November 11, 2024. The displayed weekly chart starts July 22, excluding an earlier week with four active accounts, and ends with a partial week starting November 11. Some signup records extend to December 2025 without completed activity. Full-export totals are not a strict four-month signup cohort or a count of verified unique people.

Five-contract track

The track counts accounts with a completed task for the simple contract, ERC-20, ERC-721, private token and private NFT deployment steps: 60,295 accounts, or 57.7% of active participants. A total of 76,499 completed at least one of those tasks. The simple-contract task alone has 73,804 participants. Requiring the additional three token/NFT transaction-link tasks reduces the full group to 58,592. The five-task metric does not require every optional repository, explorer or minting step.

What deployment verification establishes

The supplied methodology describes an automatic code-at-address check for the first deployment and review of the later submitted addresses. The export does not establish that every contract was deployed by the submitting account, that contracts were unique across accounts, or that the code was original. Proxy-address submissions have 8,749 distinct participants; upgrade-transaction submissions have 8,644; 8,611 completed both. The original roughly 9,500 proxy figure counts submission records rather than distinct participants.

Daily faucet and weekly streak

The custom daily faucet task contains 755,752 completion-history events from 46,697 accounts. Deduplicating to one account per UTC date gives 755,674 claim dates; 11,655 accounts have 30 or more dates. The weekly task has 17,600 distinct participants and is configured for seven consecutive daily claims. These are recorded task checks, not an independent recount of unique on-chain transactions. Faucet dates are grouped in UTC.

Later activity and eligibility

Activity means any completed task with a history timestamp. Across all 104,485 active accounts, 43,159 (41.3%) have a completion at least seven days after their first, and 21,071 (20.2%) at least 30 days later. The export’s final completion timestamp is the observation cutoff. Restricting the denominator to accounts whose first task was at least seven or 30 days before that cutoff gives 85,451 and 54,346 eligible accounts, respectively. Later activity is 50.5% and 38.8% in those groups. These are any-time-after-threshold measures, not exact-day D7/D30 retention, sessions or causal lifts. Eligible accounts still have differing total follow-up lengths.

Repository and feedback records

Repository-link tasks contain 100,586 completed records from 20,081 accounts. Of these records, 19,912 belong to a simple-contract repository task configured for automatic acceptance; the remainder belong to review-configured tasks. The total is not 100,586 distinct, reviewed or original repositories. The feedback task contains 63,400 completed records from 62,207 accounts; repeat-inclusive history contains 93,933 events. These are recorded submissions, not independently assessed unique ideas.

Review settings and duplicate records

Across all task types, there are 1,731,322 completed records and 12,437 repeated participant/task/quest records. Completion counters match history lengths, and every active account has timestamped history. Submission types account for 1,066,865 records: 1,046,953 in tasks configured for review and 19,912 in an automatically accepted task. Configuration alone does not audit each reviewer’s decision. The source’s blanket claim that all 1.07M submissions were manually reviewed is therefore narrowed.

Warm-up continuity

The earlier campaign has 4,411 accounts, of which 4,357 completed a task. It records 10,968 screenshot-proof completions across six external quest platforms and 979 mint-task participants. The testnet has 607 accounts completing a holding check against the same NFT contract. Holding that NFT does not prove that an account participated in the earlier season, because tokens can be transferred. The report’s roughly 680 returning participants is not reused: available matching methods produce different totals and do not establish a unique-person cohort.

Time-to-finish limitation

The reported completion-speed chart includes 92 accounts whose first accepted completion of all five tasks predates the account creation timestamp. Those records cannot support a valid joining-to-finish duration. The public story omits that chart rather than treating negative durations as unusually fast completions.