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 · Merlin DEX
- Sequence
- #3
- Score
- 4 → 0 (-18)
- Cluster
- mainnet-beta
- Slot
- 464365547
- Off-chain at
- 2026-11-02T04:44:56.198Z
- Anchored at
- 2026-11-02T04:45:07.000Z
- Block time
- 2026-11-02T04:45:07.000Z
Independent verification
- 1. Database (off-chain)
- 73DKw6anzyp4cALMRWfz3vo3Z8iRijyoSe7Uhtg3goYN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1450 chars)
{"actor":"judge","artifact_identity":"4e75ce54dbad3474a754d69f19a0a84b","band_override":null,"decided_at":"2026-11-02T04:44:55.816Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3636,"investigation_id":"4cde30b9-5704-47dc-b0c2-ba2a349ad0cc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"merlin","prev_score":4,"reason":"The review found 4 of 11 checked claims disputed or unverifiable (about 36%), which falls in the significant-issues band. The core account is corroborated by CoinDesk, Decrypt, DL News and Crypto.news: about $1.82M drained on April 26, 2023, the CertiK score falling from 90 to 38, and $160,000 frozen on May 4 (claim_findings[0], [4], [6]). The problems are mostly editorial or thinly sourced. The page includes leftover merged-page wording about an unsourced April 24 audit date (claim_findings[1]-[3]). The 'first time' restitution claim, the exchange-level fund-flow amounts and the ZachXBT attribution could not be verified (claim_findings[5], [8], [10]). Because the central facts hold up and reviewer confidence is moderate, the penalty is set in the lower part of the band and the page is not delisted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-18,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}