The 2026 exploit ledger, and who audited what
Build the complete, structured record of every significant crypto exploit of 2026, link each one to the contract that was hit and the audits it had, and tell the story of the year's security failures.
August 2026 was the worst month on record for crypto security: about 50 incidents and 215 million dollars lost, with the Cronos chain rolled back after the Tectonic exploit. Geo holds more than 400 Exploit entities across the Crypto and Crypto datasets spaces, but the 2026 record is incomplete, split between the two spaces, and never connected to the question everyone asks after a hack: was this audited, by whom, and what did the audit miss? This bounty builds that record and the page that tells the story.
This is a hard bounty: one curator, about six weeks. It rewards modeling judgment and sourcing, not volume.
What you build
The complete 2026 set. Every exploit from January 1, 2026 to the end of your build window with at least 1 million dollars lost, or that halted a chain, as one Exploit entity in the Crypto space. Many already exist (some only in Crypto datasets): reuse them by id, never create a second one. Add the missing ones. Expect 70 to 90 entities in total.
Every exploit fully described. Attack vector and Exploit categories (choose from the existing values), Amount lost in US dollars at the time, Amount recovered, Start date, Affected protocol (a relation to the existing project), Chain, Post-mortem URL, Outcome (one or two sentences: funds returned, fork, shutdown, insurance), Attacker identified, and at least one Source.
The audit link. For each exploit, the contract that was hit as a Contract entity (address, Network, Protocols, Explorer URL) linked from the Exploit through Contracts, and that contract's audits as Audit entities (Auditors, Completed at, Report URL, Scope, findings counts) linked through Audit reports. Where no audit exists, say so in Outcome. Correct the Auditors field on exploits where it is wrong. Target: at least 40 of the 2026 exploits with a settled answer (audited, not audited, unknown), at least 25 Contract entities, at least 20 Audit links.
The story page. A Topic "Crypto exploits in 2026": a "story so far" block of 6 to 8 sourced factual claims (the August record, the Tectonic exploit and Cronos rollback, the biggest losses, the dominant attack vectors), one table per attack vector, a month-by-month timeline, an "audited and still exploited" table, a Sources tab, a cover, and one debate proposition with 2 to 3 sourced arguments on each side. Present it at the crypto community call.
Per-entity fields
Entity
Type
Fields (relations in bold)
An exploit
Exploit (existing)
Name ("<Protocol> <what happened> exploit"), Description, Attack vector, Exploit categories, Amount lost, Amount recovered, Start date, Affected protocol, Chain, Post-mortem URL, Outcome, Attacker identified, Contracts, Auditors, Sources, Topics
A contract
Contract (existing)
Name, Contract address, Network, Protocols, Explorer URL, Is proxy, Is upgradeable, Audit reports
An audit
Audit (existing)
Name ("<Protocol> - <Auditor> - <scope> audit"), Auditors, Project, Contracts, Completed at, Report URL, Scope, Critical / High / Medium findings
A source
Article
Name, Web URL, Publish date, Publisher
Rules
Before you publish anything, share your plan with us: what you will create, what you will reuse (with Geo ids), your sources, and the outline of the page. We sign it off first.
Search before you create, in both the Crypto and the Crypto datasets spaces, every time. An automated feed is also adding exploits to Crypto datasets; if it beat you to an entity, enrich that one.
Relations, not text: protocols, chains, auditors, contracts, categories are relations to existing entities.
Every factual value has a Source with a working URL. Post-mortems and security-firm reports over press.
Amount lost is the value at the time of the incident and stays fixed. Do not store TVL, prices or other live figures as properties; if a number matters to the story, make it a dated claim with a Source.
Claims: one sentence, sentence case, no trailing period, absolute dates, name the protocol in full.
Do not delete anything; list what needs fixing and we do it.
Acceptance (mission-critical, all must pass)
No 2026 incident above the threshold missing · no duplicates of existing entities · Attack vector, categories, amount, date, affected protocol and a Source on every exploit · at least 40 exploits with a settled audit answer through real Contract and Audit entities · no live metrics stored as properties · the page tells a reader what happened this year and why, not just a table.
Reward and deadline: up to 500 points for a complete, accepted submission, quality weighted. Six weeks from allocation. One curator.