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 · TrapDoor Supply Chain Attack
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 461983454
- Off-chain at
- 2026-10-27T07:19:42.600Z
- Anchored at
- 2026-10-27T07:19:48.000Z
- Block time
- 2026-10-27T07:19:48.000Z
Independent verification
- 1. Database (off-chain)
- ERdpH3avEmRERmYfQZFHoA4Ayb7CpiZes8intdQhrkgF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1430 chars)
{"actor":"reviewer","artifact_identity":"2a960ae7d6359b8fae4595ff5bfdba40","blocked_count":1,"decided_at":"2026-10-27T07:19:42.235Z","decision":"review","disputed_pct":0,"findings_hash":"8v4drZXKzHzZ5QPJbJsqe9CcWcFgjNRQjS9jwDwYgwPw","investigation_id":"56eb1ee0-9db3-408e-9230-533176068d1b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":0,"total":1},"page_content_hash":"1783b597e671f4188e4775fcbe0d1514b6fd3e9b1fd0e551b5bc94ce371444b9","page_slug":"trapdoor-supply-chain-attack","prev_score":0,"reason":"The technical core (package counts and names, trap-core.js size, detection statistics, the six targeted repositories, the no-victims statement) matches Socket's report and The Hacker News. Problems are attribution and dating. The summary credits Socket with a SlowMist-style superlative that Socket's report does not contain. The 2026-05-29 reporting date and the 'initial coverage' label for The Hacker News are not supported, since Socket published on May 24. The SlowMist quote could not be checked because the source returned 403.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}