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 · Spark Protocol
- Sequence
- #2
- Score
- 72 → 72 (0)
- Cluster
- mainnet-beta
- Slot
- 424082429
- Off-chain at
- 2026-06-03T18:38:35.367Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2VvYoEyrbe8Gxy51tW2Hc4KMrtBKjXwwJRe4rhdEHk35
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1075 chars)
{"actor":"reviewer","decided_at":"2026-06-03T18:38:34.981Z","decision":"review","investigation_id":"3521d213-41a5-4bce-9fc5-f69f6eea70d2","new_score":72,"page_slug":"spark-protocol","prev_score":72,"reason":"The page is broadly accurate on protocol architecture, tokenomics, governance concentration, audit history, and institutional pivot. The most significant factual error is the claim that SPK's all-time high of ~$0.1774 occurred 'on launch day' and that the price dropped over 70% within hours — in reality, the ATH was ~$0.1845 reached on July 23, 2025, over a month post-launch, and launch-day decline was approximately 54%. A secondary issue is the Kelp bridge exploit being framed as occurring in 2025 when it actually happened in April 2026. One primary cited source (CoinTelegraph VPN article) returns 404, constituting link rot on a key claim, though the underlying facts are corroborated by redundant secondary sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}