Use the public Receipt API
Create a known-answer or failure-path receipt with the documented HTTP endpoint and save its digest.
27 / Developer adoption
This public sprint measures proposals, receipt publication and independent reproductions. It does not measure token purchases, trading volume, impressions or paid engagement.
01 / Live baseline
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
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
Create a known-answer or failure-path receipt with the documented HTTP endpoint and save its digest.
Publish source, environment, command, expected result, observed result and limitations without credentials or private data.
The public leaderboard changes only after PactVerity can reproduce the submitted package.
04 / Excluded signals
Public work queue