27 / Developer adoption
Thirty days to produce evidence another developer can reproduce.
This public sprint measures proposals, receipt publication and independent reproductions. It does not measure token purchases, trading volume, impressions or paid engagement.
Sprint29 Aug–28 SepEntry feeNonePVTY rewardNone
01 / Live baseline
Every count starts from the public register.
Private contact details are excluded. Counts refresh from the same D1-backed APIs used by the public challenge and programme status pages.
02 / Thirty-day objectives
Four targets—clearly separated from achieved results.
Targets are programme objectives, not current adoption claims or forecasts.
| Measure | Baseline | 30-day objective | Counting rule |
|---|---|---|---|
| Distinct public proposals | 4 | 10 | D1-backed developer application register; duplicates normalized by project and track. |
| Published receipt hashes | 0 | 20 | Valid, self-consistent receipts voluntarily published through the public API. |
| Receipt Challenge submissions | 0 | 5 | Public repositories and exact reproduction commands received for review. |
| Independently reproduced entries | 0 | 3 | Entries published only after the command, evidence and receipt digest are reproduced. |
03 / Start here
Build, publish and invite reproduction.
Step 01Run
Use the public Receipt API
Create a known-answer or failure-path receipt with the documented HTTP endpoint and save its digest.
Step 02Publish
Expose the exact evidence
Publish source, environment, command, expected result, observed result and limitations without credentials or private data.
Step 03Challenge
Submit for independent review
The public leaderboard changes only after PactVerity can reproduce the submitted package.
04 / Excluded signals
Trading is not developer adoption.
- No token purchase, wallet connection or PVTY holding is required.
- No trading-volume, holder-count or price target appears in the sprint score.
- No paid engagement, undisclosed sponsorship or manufactured submission is counted.
- No first-party test is described as an independent integration or security audit.
Public work queue