A COMMUNITY PROOF CAMPAIGN

Contribute evidence, not trust

ProofDama is a project in progress. Independent reviewers and hardware contributors can help it advance, but every result must still survive the same public certificate and replay gates.

Current verifiable state

Three rungs contain 5,756,836 independently replayed nodes. The active 6×4×1 campaign runs independently on a scheduled 12-thread M4 Max and a low-priority Hetzner worker. Its historical draw is not certified yet.

Four useful contributions now

01

Reproduce

Run the judge demo or replay a published certificate and report any ARM64 / x86-64 difference.

02

Review

Audit the FID rules, certificate schema, canonical reindexing, or adversarial checks. A documented counterexample is a valuable contribution.

03

Compute

Offer CPU, RAM, or storage through a versioned job with a frozen source commit, resource limits, checkpoints, and logs.

04

Fund

Support CPU time, storage, and artifact publication transparently. Funding never purchases a result or bypasses independent replay.

AUTHORIZED CONTACT

Join the ProofDama campaign

Use this form to offer hardware, scientific review, documentation, or funding. Your message is delivered through the project’s official Formspree form.

No unauthorized email address is published on this website.

Hardware contribution contract

A community worker receives a frozen repository commit, benchmark, node budget, thread budget, and checkpoint directory. It returns only logs and a content-addressed artifact. ProofDama accepts that artifact only after a separate verifier regenerates every legal edge and a second architecture reproduces the hash where required.