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
Adoption boundary:An application is not a selection. A submission is not an integration. Only an independently reproduced public entry moves the verified counter.

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.

Loading the public adoption baseline…

02 / Thirty-day objectives

Four targets—clearly separated from achieved results.

Targets are programme objectives, not current adoption claims or forecasts.

PactVerity developer adoption sprint baseline and objectives
MeasureBaseline30-day objectiveCounting rule
Distinct public proposals410D1-backed developer application register; duplicates normalized by project and track.
Published receipt hashes020Valid, self-consistent receipts voluntarily published through the public API.
Receipt Challenge submissions05Public repositories and exact reproduction commands received for review.
Independently reproduced entries03Entries 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.

Open the developer guide

Step 02Publish

Expose the exact evidence

Publish source, environment, command, expected result, observed result and limitations without credentials or private data.

Reproduce the benchmark

Step 03Challenge

Submit for independent review

The public leaderboard changes only after PactVerity can reproduce the submitted package.

Submit a challenge entry

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

Choose a reproducible developer task.

Open GitHub issues