Challenge Ledger · Open · Unfunded · Peer-Audited

Run it. Break it.
Tell us what you find.

The canonical claims are public. The benchmark is open-source. The ledger is open to every replication, positive or negative. No cash bounties. Co-authorship instead.


Canonical claims

#ClaimValueWhitepaperSHA-256
1DRAM working set multiplier4.1445×WP-1e435686a…d2f1
2Water conservation97.6%WP-2fbf0ef6c…badea
3Zero-copy IPC · resident bus11.1 µsWP-31743f9fc…4428
4Zero-copy IPC · 4-hop nominal65.9 µsWP-31743f9fc…4428
5Sub-cycle grid defense45 MW / 16.7 msWP-40f5f6572…c7c8
Honesty constraint. Every value above is formula, derivation, or model — per manymoats.com/papers. Not a meter reading. Replication is the test.

Replication protocol

1
Run
Open ./battlegrounds.html in any modern browser. No install. No account. No telemetry.
2
Compare
Within ±10% → replicated. Outside ±10% → refuted or configuration difference.
3
Submit
Email ledger@manymoats.com with hardware config, raw output, methodology, interpretation.
4
Publish
Replicated → co-author next revision. Refuted → co-author correction. Inconclusive → co-design better test.

Ledger

DateClaimTesterHardwareResultStatus
—————Open for submissions

Negative results published with equal prominence. Living document.

What we will not do

No cash bountiesCash attracts bounty farmers. Co-authorship attracts people who care about the truth.
No suppressed negativesFalsify a claim → we publish it and update the canonical value.
No attacks on criticsFind a flaw → you are doing us a favor. Try to break it now.
Submit replication GitHub benchmark Papers
Challenge Ledger v1.0 · 2026-09-28
ledger@manymoats.com · manymoats.com/papers