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
- Sequence
- #3
- Score
- 18 → 6 (-12)
- Cluster
- mainnet-beta
- Slot
- 462172170
- Off-chain at
- 2026-10-27T18:28:27.239Z
- Anchored at
- 2026-10-27T18:28:45.000Z
- Block time
- 2026-10-27T18:28:45.000Z
Independent verification
- 1. Database (off-chain)
- 7ktMsFJYsZY1ZMXvAXFwYGVw3YRqpdMiq9iiaFpzXYR4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1633 chars)
{"actor":"judge","artifact_identity":"5176d31f4e74f0332b6697b9b4dfc880","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:28:26.925Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2667,"investigation_id":"c3a7fc22-c67a-4dc2-a6f6-d0ce0a0dc365","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":6,"page_slug":"meter-io-passport-bridge-block-validation-exploit-september-2026","prev_score":18,"reason":"Of 15 scored claims (one unreadable source excluded), 4 were disputed or could not be verified, about 27%, which falls in the minor-issues band. The core incident facts (the $2.3M unbacked wMTRG, the block 100731417 notice, the 10% bounty, the MTRG price drop, the 2022 precedent) are supported by secondary outlets. However, claim_findings[0] shows the 'third' attacker address is the first address in different letter case, and claim_findings[1] shows the Etherscan exploiter link belongs to the 2022 incident, not 2026. The bridge contract address and Phemex percentages could not be verified (claim_findings[7], [10]), and the start time conflicts between sources (claim_findings[2]). Two high-priority coverage gaps remain: no first-party Meter source and no on-chain transaction evidence. The omission of follow-up since 24 Sept is minor, and the subject status does not contradict the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"scored_claims":15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}