Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
review_approve · MakerDAO Legacy Auction Keeper Exploit (October 2026)
- Sequence
- #3
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 462054589
- Off-chain at
- 2026-10-27T11:31:44.671Z
- Anchored at
- 2026-10-27T11:31:55.000Z
- Block time
- 2026-10-27T11:31:55.000Z
Independent verification
- 1. Database (off-chain)
- J5zEiVuVC1YoUVbxUdWSZ5jRNVLPxjwxaQbpLTz6UHPR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1457 chars)
{"actor":"judge","artifact_identity":"c53b5bdde8202fdca4e32eaf3e9a64dd","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:31:44.104Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"02ccd163-e530-4447-b984-8da8fb7e1fd5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"page_slug":"makerdao-legacy-auction-keeper-exploit-october-2026","prev_score":35,"reason":"Of 11 claim findings, 1 could not be checked because the source (Crypto Times) blocked the reviewer and was left out of the count; of the remaining 10, none were disputed or unverifiable, giving 0% disputed. The core facts (200 ETH loss, 6 October 2026 timing, selector 0x8804d1de, auctions 1457-1460, missing access check, Tornado Cash funding) were confirmed against CertiK and Protos (claim_findings[0-4, 8-9]). Two findings were partially supported: the exploit step-level detail (claim_findings[2]) and the Tornado Cash batch count (claim_findings[5]), which also contains a stray reference to 'the requester' that should be edited out. The only omission is minor, and the page's subject status (exploited) is already reflected on it.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}