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 · Axios npm Supply Chain Attack (March 2026)
- Sequence
- #3
- Score
- 4 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 462186906
- Off-chain at
- 2026-10-27T19:20:29.942Z
- Anchored at
- 2026-10-27T19:20:53.000Z
- Block time
- 2026-10-27T19:20:53.000Z
Independent verification
- 1. Database (off-chain)
- DSNsF4HbnDrfBwmZKdDPQshvrWpjzQDqRAFdV56X3scT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1625 chars)
{"actor":"judge","artifact_identity":"d5471ee2ba5d6750985d1e1c20322361","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:20:29.537Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"8db5fc64-aacd-406c-807b-9fb98cf7530e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"axios-npm-supply-chain-attack-march-2026","prev_score":4,"reason":"The core incident facts hold: the malicious versions and UTC timeline match the official post-mortem (claim_findings[0]), and the Microsoft, Google and CISA statements were confirmed (claim_findings[6], [7], [8]). Of 12 findings, 1 was left out of the count because the source refused the reviewer; of the remaining 11, one is disputed (the Unit 42 hash count is 24 unique, not 23, claim_findings[5]) and one could not be verified (the 23:59 UTC time for plain-crypto-js@4.2.1, claim_findings[1]), giving about 18%. Three further claims were only partly supported: the 174,000 dependents and 80% environment figures are not in the cited sources, and the statement that no count of compromised systems exists is contradicted by vendor telemetry (claim_findings[2], [3], [4]). The delta sits mid-band because these scale and impact figures are prominent, but none of them touches the central attribution or timeline.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"scored_claims":12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}