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
0 → 0 (-18)
Cluster
mainnet-beta
Slot
465100792
Off-chain at
2026-11-04T00:29:57.566Z
Anchored at
2026-11-04T00:30:16.000Z
Block time
2026-11-04T00:30:16.000Z

Independent verification

1. Database (off-chain)
4KgDBx2W684z54Kf1iVvRanueQVRuoNBqaGEz7viwKyQ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1566 chars)
{"actor":"judge","artifact_identity":"563fde4686e0f3d9f92e411d2097d672","band_override":null,"decided_at":"2026-11-04T00:29:57.326Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"7f614e32-5f72-4495-923a-46890c56396d","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"isis-nigeria-turkey-crypto-financing-entities-nine-to-nine-manhattan-bureau-generation-currency-spider-alkaram","prev_score":0,"reason":"The core facts hold up: the June 22, 2026 OFAC designations under E.O. 13224, the ownership links and the sanctioned status of all five entities match the Treasury release. However, 3 of 9 claims (33%) could not be verified: Muhammad's date of birth, address and passport numbers (claim_findings[1]), the two TRON wallet strings (claim_findings[5]) and the European-diaspora characterization of Spider and Alkaram (claim_findings[6]). Several other claims go beyond their sources, including the 'front company' wording, the $10 million figure that is TRM's attribution rather than an OFAC allegation, and the individual count that repeats an inconsistency in Treasury's release. The high-priority gap, citing the SDN entries for the identifiers and wallet addresses, pushes the penalty toward the lower-middle of the band.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-18,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}