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 · fake Ledger Live app
- Sequence
- #3
- Score
- 0 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 462280052
- Off-chain at
- 2026-10-28T00:51:21.064Z
- Anchored at
- 2026-10-28T00:51:51.000Z
- Block time
- 2026-10-28T00:51:51.000Z
Independent verification
- 1. Database (off-chain)
- 4sKn5ET5WX4QCvQwpet111oPjKTe1ihdZFaGGMbesbkV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1329 chars)
{"actor":"judge","artifact_identity":"ea00ef3e30f5e8ae621035d17fc41bf8","band_override":null,"decided_at":"2026-10-28T00:51:20.833Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4,"investigation_id":"80a8e14e-8976-44ff-9253-740a398fbbd5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"fake-ledger-live-app","prev_score":0,"reason":"Four of ten checked claims (40%) could not be found in the sources the page cites (claim_findings[1], [2], [5], [9]), which places the page in the significant-issues band. The two headline incidents, $768,000 via the Microsoft Store and $9.5 million via the Apple App Store, were confirmed by a Tier 1 source (claim_findings[0], [3]), and no claim was contradicted. Because the reviewer's confidence was low (0.5) and one of the four unverified items was not fetched at all, the penalty is set at the mild end of the band. Several details were only partly supported (the two-week live period, the KuCoin freeze, the G. Love date), and the page should be corrected or re-sourced.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}