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 · A7A5 Stablecoin / Old Vector
- Sequence
- #3
- Score
- 0 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 461972998
- Off-chain at
- 2026-10-27T06:42:28.335Z
- Anchored at
- 2026-10-27T06:42:42.000Z
- Block time
- 2026-10-27T06:42:42.000Z
Independent verification
- 1. Database (off-chain)
- FZNHjqHYfExpUH9bei5DUh7EHNXPTJ1ADUMRDJWHJZxh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2023 chars)
{"actor":"judge","artifact_identity":"2d46eef1bb1da4f5714c36baef402188","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T06:42:27.793Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"1895b94b-3df1-4c1f-a840-b7073d45c494","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"a7a5-stablecoin-old-vector","prev_score":0,"reason":"Of 9 claim findings, 1 was excluded as source_blocked (the Council of the EU page returned 403), leaving 8; 1 is disputed (claim_findings[0]: the UK 18-target package is dated May 26, 2025 in the sanctions section but was May 26, 2026 per GOV.UK and CoinGeek), giving disputed_pct of 12.5%, the minor band. Two further findings were only partially supported: the statement that A7A5 tokens are blocked property goes beyond the Treasury release (claim_findings[1]), and the Cooper quote was not found on the cited GOV.UK page (claim_findings[2]). The core OFAC designations, Garantex history and Elliptic collapse metrics were confirmed, and the page omits the EU 21st package of July 23, 2026, which should be added. Only a sample of a very large claim set was checked (reviewer confidence 0.55), so the penalty stays at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"scored_claims":8,"sequence_num":3,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The review reports a material omission (the EU 21st package of July 23, 2026, four further A7-linked designations) but subject_status.contradicts_page is false: the page already presents Old Vector and the A7 network as sanctioned by the US, UK and EU, and the omitted item adds to, rather than changes, that picture. The omission is handled as a requested addition, not as grounds for a harsher band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}