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 · Ledger
- Sequence
- #5
- Score
- 58 → 51 (-7)
- Cluster
- mainnet-beta
- Slot
- 462048324
- Off-chain at
- 2026-10-27T11:09:34.493Z
- Anchored at
- 2026-10-27T11:09:40.000Z
- Block time
- 2026-10-27T11:09:40.000Z
Independent verification
- 1. Database (off-chain)
- 1BgVarCTAarR9Kh9prMFrYYjJ8FHxAq33ATg55tkRX7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1943 chars)
{"actor":"judge","artifact_identity":"53f7cc1de4bb4212f6609544412b3ef0","band_override":null,"decided_at":"2026-10-27T11:09:34.040Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"ledger","prev_score":58,"reason":"Counting 2 unverifiable findings out of 7 claim findings gives about 29% (claim_findings[4] and claim_findings[6], both not_found, neither source_blocked), which falls in the minor band. The most important defect is claim_findings[0]: the page says Ledger is preparing a US IPO, but May 2026 reporting says it paused. claim_findings[1] also notes that the 270,000-address figure is attributed to Ledger's own notice, which gives about 9,500 customers. The core incident chronology (2020 breach, fake App Store app) was confirmed against Tier 1 and Tier 2 sources, and the reviewer's own confidence is limited (0.5) because several claims were not verified in depth.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-7,"score_limit":{"applied":-7,"limited":true,"proposed":-12,"rule":"limited_no_second_opinion","second":null},"sequence_num":5,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"The review reports subject_status.contradicts_page: the summary and company background say Ledger is preparing a US IPO, while May 2026 reporting says it paused the plan. Ledger is still operating with no sanction or shutdown, and the omissions are rated minor, so the page is held in the minor band rather than moved to significant. The contradiction is why the delta sits toward the harsher end of that band and why the verdict is not approve."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}