Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#3
Score
10 → 0 (-20)
Cluster
mainnet-beta
Slot
462180508
Off-chain at
2026-10-27T18:58:03.468Z
Anchored at
2026-10-27T18:58:13.000Z
Block time
2026-10-27T18:58:13.000Z

Independent verification

1. Database (off-chain)
EWQiQHeTrSatGiFxb9rDmnzwRpawLsXj3vzY9EN3NMVy
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1796 chars)
{"actor":"judge","artifact_identity":"8ff10f1b525def35d25c75da5f0e732f","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:58:03.211Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4375,"investigation_id":"26a30bbc-ac0b-405d-a0e0-00f55a3cf1f4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"defi-price-manipulation-exploit-wave-record-32-attacks-in-2026","prev_score":10,"reason":"Of 16 scored claim findings (one blocked-source finding excluded), 3 are disputed and 4 are unverifiable, giving 7/16 or about 44%. The disputed items include the Cronos rollback amount in the body and the timeline (claim_findings[2], [4]) and a median loss figure attributed to the wrong population (claim_findings[7]). The unrecovered-funds figure is also stale (claim_findings[3], [5]), and a material omission means the page understates the Tectonic loss (omission_findings[0]). The headline claims hold (TRM's 32 attacks, Tectonic at about $75M at first report), and the reviewer's confidence is moderate, so the penalty sits mid-band and the page is not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-20,"scored_claims":16,"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission: the Cronos post-mortem puts the Tectonic borrowing at about $120.4M and the rollback at about $111.2M, against the page's $75M and $68.7M. This agrees with the significant band implied by the percentage, so the band is held at significant rather than lowered."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}