23 / Receipt Challenge
Reproduce it. Challenge it. Publish the evidence.
A free technical challenge for independent developers. There are no PVTY rewards, trading requirements or paid placements. Leaderboard entries are published only after the evidence can be reproduced.
Entry feeFreeToken rewardNoneVerificationRequired
01 / Live programme
The public leaderboard begins at zero.
Counts come from the live challenge register. Private contact details and unverified entries are never displayed.
Verified public leaderboard
No verified external run is published yet.
The leaderboard starts at zero and changes only after the submitted command, environment, evidence and receipt digest are reproduced.
02 / Review rubric
Four gates prevent inflated claims.
1. Public inputs
The repository, evidence and claimed result must be accessible without credentials or private customer material.
2. Exact reproduction
The submitted environment and command must execute without undocumented manual intervention.
3. Matching commitment
The reproduced receipt must match the disclosed SHA-256 commitment and expected pass or failure path.
4. Limits disclosed
The final entry records limitations and does not convert a test into a customer, revenue, audit or production-integration claim.
03 / Seven-day activation
One technical proof each day—no trading incentive.
This schedule is designed to create reproducible product evidence that developers can challenge publicly.
Days 1–2
Publish the known-answer input, expected receipt and one deliberately tampered case. Invite reproduction, not investment.
Days 3–5
Show JavaScript, Python and edge-runtime reproductions with the exact environment and commands.
Days 6–7
Publish verified external entries, unresolved failures and a weekly evidence summary without converting submissions into integration claims.