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 · Spark Protocol
- Sequence
- #3
- Score
- 72 → 62 (-10)
- Cluster
- mainnet-beta
- Slot
- 424082432
- Off-chain at
- 2026-06-03T18:38:35.468Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4NBihQJfFAxTW6DV6SCu3xnyoR3jUNE1TxrdQzjAxHUi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1335 chars)
{"actor":"judge","decided_at":"2026-06-03T18:38:34.981Z","decision":"review_revise","investigation_id":"3521d213-41a5-4bce-9fc5-f69f6eea70d2","new_score":62,"page_slug":"spark-protocol","prev_score":72,"reason":"The page is broadly accurate on protocol architecture, governance, audits, and institutional activity, with 20 of 28 claims confirmed. Two claims in the SPK token section (claim_findings[10] and claim_findings[11]) are disputed by Tier 1 and Tier 2 sources: the page states SPK's all-time high of ~$0.1774 was reached on launch day and that the price dropped over 70% within hours, but CoinGecko places the actual ATH at $0.1845 on July 23, 2025 — over a month post-launch — and the launch-day decline was approximately 54%, not 70%+. A secondary factual error (claim_findings[24], partially supported) places the Kelp bridge exploit in 2025 when it occurred in April 2026, creating a misleading framing in the security section. One primary citation (CoinTelegraph VPN article) has confirmed link rot, though the underlying claims are corroborated by secondary sources. A high-priority coverage gap flags the SPK price error as requiring correction with a proper source citation.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}