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
- #5
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 462186373
- Off-chain at
- 2026-10-27T19:18:30.336Z
- Anchored at
- 2026-10-27T19:19:01.000Z
- Block time
- 2026-10-27T19:19:01.000Z
Independent verification
- 1. Database (off-chain)
- 5So4rzDAp6geAFU4LBVKmg3SiJ2y4ez5AJegJa5oVFnQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1698 chars)
{"actor":"reviewer","artifact_identity":"6de93add3bbe528145e6ed6149b4caed","blocked_count":1,"decided_at":"2026-10-27T19:18:30.131Z","decision":"review","disputed_pct":0.0833,"findings_hash":"63JA2KABzSsGvtCfksurm6pnLmnB1dpxrFPnY6uUA2L","investigation_id":"9b3e7fc9-d98c-4d79-8b5d-852d1bd6f02b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":1,"total":1},"page_content_hash":"85e7f3dc3b500ea4af928fe9444726d4cef20befbf6245468061d1c932c332d0","page_slug":"chaindrop-mini-shai-hulud-npm-supply-chain-worm-august-2026","prev_score":0,"reason":"The core narrative holds up where checked: the keyv maintainer account compromise, the preinstall and Bun delivery, the Ethereum contract C2 and the Unit 42 attribution caveat all match primary vendor sources. The main defects are a stale law-enforcement statement, since TeamPCP arrests were reported in late August; a conflation of C2 domain registration (May 22) with infrastructure deployment (contract on May 25); and several attributions to specific vendors, such as Elastic's counts and timestamp and Unit 42's credential-pattern and wallet.dat details, that the fetched text did not support. The NHS alert could not be read, and its archive date suggests it may concern an earlier wave. The page is very long and dense, and only a sample of claims was checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}