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_approve · Blur Finance
- Sequence
- #3
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 426255449
- Off-chain at
- 2026-06-13T18:42:55.136Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 69G91oDyYJwUT93fdoVeHnTsmTi3mS1Mzg9xwpDh6QdH
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1251 chars)
{"actor":"judge","decided_at":"2026-06-13T18:42:54.763Z","decision":"review_approve","investigation_id":"5885afbd-3fec-4be4-a732-12b9cfb3e382","new_score":2,"page_slug":"blur-finance","prev_score":2,"reason":"The reviewer found 0 disputed claims across 12 assessed claims, placing this page firmly in the 0%–10% approval band. All core allegations — the $600K rug pull, dual-chain operation on BNB Chain and Polygon, 99% token collapse, developer disappearance, and block explorer labels — are confirmed by at least one Tier 1 source (CoinDesk, BscScan, PolygonScan). The four partially-supported findings (claim_findings[5], [8], [10], [11]) are minor in nature: a plausible but unconfirmed DEX attribution, a one-day timing ambiguity, an address label specificity nuance, and a disambiguation citation for an unrelated project. None of these undermine the page's factual core. Two high-priority coverage gaps (on-chain wallet tracing, developer de-anonymization) are noted but gaps of this type indicate expansion opportunities, not grounds for denial. Reviewer confidence of 0.85 supports a clean approval.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}