$1,000 if you forge a PROOFLOOP record

The target

Everything you need is public. Download it into an empty folder:

Copy

The genuine record prints RESULT: ALL RECORDS VALID. Change its verdict, its code, a test result, its hash or its signature, and it prints RESULT: TAMPERED OR INVALID. Your job is to get ALL RECORDS VALID anyway.

• Verifier: verify_keystone.py, SHA-256 da0dbe31996168011aeeb3d3851a10185ea8271f58e72ada8cd630f85624a50d (this exact file; it imports none of our code).
• Pinned key: b6hfA2rpAdV29FOdhNXGkk4t91mCV0AnfFYwq0HO0R8=, fingerprint SHA256:2232b4add9b35d4016e5be270df4ed56e0dc9b39a0530ac69891073253aae90d, the same key logged in Sigstore Rekor entry 3742368068.
• Machine-readable terms and hashes: bounty.json.

What counts as a win

1. You send us a record file (JSON) that the pinned verify_keystone.py, run with the pinned key exactly as shown above, reports as VALID with RESULT: ALL RECORDS VALID.
2. That record's content, as the verifier parses it, is not identical to any record issued by the FIRME AI CORPORATION signing service. Editing the published target record and still passing is the obvious way to win.
3. We can reproduce it on a clean machine with Python 3.10 or newer and the current cryptography release.

What does not count

• Getting the private key, or a signature, by attacking our servers, accounts, staff, suppliers or anyone else. Do not test our live systems for this challenge, and do not try denial of service or social engineering.
• Records that our public services genuinely issued and signed, including through the public demos. Those are real records, not forgeries.
• Running a different verifier, an edited verifier, a different key, or skipping --pinned-pub.
• A real record shown with misleading text around it, or a JSON file whose raw text reads differently from what the verifier parses (for example duplicate keys) when the parsed content matches a real record.
• Anything illegal where you or we are, or anything that harms other people.

Found a different problem, for example a proof that passes when the fix is wrong? Please send it too. It is outside this $1,000 challenge, but we will thank you publicly (with your permission) and fix it in the open.

How to claim, and how we pay

1. Email the record file and the exact command you ran to firmeai2026@gmail.com. Keep it private until we answer, at most 14 days.
2. We run the pinned verifier on your file and reply within 7 days. If it wins, we publish the result, the fix, and your name if you want it credited.
3. One prize in total: $1,000 to the first valid claim, by time of our receipt. FIRME AI CORPORATION pays within 30 days of confirming the win, by a method we agree with you. We may need the tax information the law requires. Members of our team cannot win.
4. The challenge closes 2027-02-28 23:59 UTC, or when the prize is paid, whichever comes first. The status here and in bounty.json is updated when either happens.

Why we can offer this

The record is canonical JSON hashed with SHA-256; the hash is signed with Ed25519; the verifier recomputes the hash and checks the signature against a key you pin yourself. Forging one means breaking Ed25519 or finding a flaw in a 341-line verifier you can read in ten minutes. We would rather you find that flaw than a customer's auditor.

Warm up: break it in your browser Or get your own fixes proved: from $149