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_revise · Anibal Alexander Canelon Aguirre
- Sequence
- #7
- Score
- 0 → 0 (-7)
- Cluster
- mainnet-beta
- Slot
- 465061690
- Off-chain at
- 2026-11-03T22:10:09.126Z
- Anchored at
- 2026-11-03T22:10:38.000Z
- Block time
- 2026-11-03T22:10:38.000Z
Independent verification
- 1. Database (off-chain)
- FWiNCHqJU887rWvhowRjcG5pGr2ooXhneaNQD6rHJ5yC
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1567 chars)
{"actor":"judge","artifact_identity":"f5ef19e3ca09b87c9f5b36b1d4ddd9f2","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T22:10:08.817Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"d2b0b032-44a1-4810-ba87-4831364b0548","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"anibal-alexander-canelon-aguirre","prev_score":0,"reason":"No claim was disputed. Of the five checkable claims, one (claim_findings[3], the 30-year maximum on the bank fraud count) could not be confirmed because the cited KTIV source was not retrieved, which gives 20% unverified. One further claim (claim_findings[5], the OCCRP court schedule) was left out of the percentage because the source blocked the reviewer. That is a coverage limit, not a defect of the page. The core allegations (OFAC designation, indictment, not-guilty plea, detention, Ploutus attribution caveat) match the OFAC page and The Record. The page's loss-figure caveat is overly cautious (claim_findings[2]) and a minor omission leaves out the 117-attack, $5.4M figure. The case-status information may be stale after the October 30 hearing. The penalty is small because the unverified item is a secondary detail and the reviewer's confidence is moderate.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-7,"scored_claims":5,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}