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.
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 465104704
- Off-chain at
- 2026-11-04T00:43:56.720Z
- Anchored at
- 2026-11-04T00:44:15.000Z
- Block time
- 2026-11-04T00:44:15.000Z
Independent verification
- 1. Database (off-chain)
- 864QLurTCeGFKAk3StAyavxRqznvrkxZDrRmEPHGeK57
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1248 chars)
{"actor":"reviewer","artifact_identity":"dbd9a8fc60fc3f37d3817fa7db3f90ca","blocked_count":1,"decided_at":"2026-11-04T00:43:56.631Z","decision":"review","disputed_pct":0,"findings_hash":"Ey4161KeLhs1RA68sJ1u8mpqNMXcgisbD7AsyfY2p73e","investigation_id":"905023a0-e0e6-4b7f-84aa-1e4336c03c59","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"omissions":{"material":1,"total":1},"page_content_hash":"d27462468eb9aa6f080b169be0a316656571de7d5e975193de4782b097b70b1e","page_slug":"npm-debug-chalk-supply-chain-attack-september-2025","prev_score":0,"reason":"Core facts checked (18 first-wave packages, ~$600 theft, second-wave packages) match The Hacker News. The attribution section is stale: Amazon attributed the attack to Sapphire Sleet in July 2026. Detailed timeline times and IOCs could not be verified because Sygnia blocked the fetch; only a limited sample of claims was checked.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":4,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}