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 · Electrum
- Sequence
- #4
- Score
- 68 → 68 (0)
- Cluster
- mainnet-beta
- Slot
- 461974684
- Off-chain at
- 2026-10-27T06:48:36.357Z
- Anchored at
- 2026-10-27T06:48:42.000Z
- Block time
- 2026-10-27T06:48:42.000Z
Independent verification
- 1. Database (off-chain)
- BNUUJuHPdFRadFTsFcvD43jQTYXCMxA5ZZwts1LNsnBx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1970 chars)
{"actor":"judge","artifact_identity":"f8052da16d72533fbe9bc622b92781d9","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T06:48:36.018Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2,"investigation_id":"59ae77cf-e939-46d3-a374-83e01f3e03e9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":68,"page_slug":"electrum","prev_score":68,"reason":"Of the 5 scoreable claim findings (one was excluded because the source blocked the reviewer), 1 is unverifiable and 1 is stale, so about 20% are unresolved, which falls in the minor band. The core phishing-loss, botnet and police-investigation figures were confirmed against Decrypt and The Hacker News (claim_findings[2], [3], [4]). The page's 'current release 4.6.2' statement is out of date (claim_findings[0]), the 4.6.2 release date could not be verified (claim_findings[1]), and the page omits the 2026 security releases (omission_findings[0]). Two high-priority coverage gaps and low reviewer confidence (0.5) support a revision with a moderate penalty, not a harsher band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":5,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (2026 security releases, 4.8.x) and the stale 'current release' statement are real, but they rest on a single Tier 3 secondary source that was not confirmed against electrum.org or the project's advisories. The project is operating, with no shutdown, sanction or exploit of the project itself. The omission concerns recent patch history and does not change the documented 2018-2020 incidents. The minor band already gives a revise verdict, and the delta is set near the top of that band to reflect the omission."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}