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 · ChainDrop / Mini Shai-Hulud npm Supply Chain Worm (August 2026)
- Sequence
- #6
- Score
- 0 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 462186378
- Off-chain at
- 2026-10-27T19:18:30.497Z
- Anchored at
- 2026-10-27T19:19:02.000Z
- Block time
- 2026-10-27T19:19:02.000Z
Independent verification
- 1. Database (off-chain)
- DEubrSKsjL6Jb1u7CCnZ7dW9aiED54yn7DireDjWhZLB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1955 chars)
{"actor":"judge","artifact_identity":"6de93add3bbe528145e6ed6149b4caed","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:18:30.131Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0833,"investigation_id":"9b3e7fc9-d98c-4d79-8b5d-852d1bd6f02b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"chaindrop-mini-shai-hulud-npm-supply-chain-worm-august-2026","prev_score":0,"reason":"Most checked claims match primary vendor sources: the keyv account compromise, the Bun and preinstall delivery, the Ethereum contract C2, the Microsoft and CSA Singapore advisories, and the Unit 42 attribution caveat. The percentage alone would approve the page, but claim_findings[1] shows the statement that no law enforcement action had been announced is out of date, since two alleged TeamPCP members were arrested on August 26, 2026. The reporting does not link those arrests to ChainDrop. Several vendor attributions are also only partly supported (claim_findings[2], [4], [5]), and the NHS alert could not be read. These issues justify a minor penalty and a correction pass, not a denial.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"scored_claims":12,"sequence_num":6,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Counting 13 claim findings, with the one source_blocked finding excluded, 1 of 12 is unverifiable and none is disputed, giving about 8% (approve band). The review reports a material omission (August 26, 2026 TeamPCP arrests) and subject_status.contradicts_page is true, because the page says no law enforcement action had been announced. A high-priority coverage gap on post-August developments points the same way. The band is raised to minor."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}