Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Stellar
View on Solana ↗
Sequence
#5
Score
89 → 89 (0)
Cluster
mainnet-beta
Slot
457851517
Off-chain at
2026-10-17T01:20:01.960Z
Anchored at
2026-10-17T01:20:13.791Z
Block time
—

Independent verification

1. Database (off-chain)
3JjZEV7mUg4DvAebXsKbWauRiueVLtuXEVN2jwU7kGBw
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1960 chars)
{"actor":"reviewer","artifact_identity":"d5f9a90202a24e5c0ec7cc8308a26a44","decided_at":"2026-10-17T01:20:01.787Z","decision":"review","disputed_pct":0.3529,"findings_hash":"EqHKk3yFuSp8DZmmLk7bajJynN6ZGH5iPqMU6nkhvuKi","investigation_id":"bf37a4c8-4dc0-4158-a207-b4f89b78ed95","mode":"findings_only","new_score":89,"page_content_hash":"ad73629f8fa84a53e240769a100566910fa53caf7faf5ea4769813e17414266b","page_slug":"stellar-xlm","prev_score":89,"reason":"Most of the page's historical and factual claims (founding, Soroban launch timing, the 2019 burn, the BlackWallet and StellarOrg Twitter incidents, the October 2025 Soroban Protocol 23 post-mortem, McCaleb's founder history, and Dixon's December 2024 House testimony) are well supported by the cited sources and corroborated independently. The most significant problems are in the 'Token Distribution and Centralization' and 'Partnerships and Institutional Adoption' sections: the ~77 validator figure is unsupported by any source found and conflicts sharply with SDF's own reported node counts, and the MoneyGram $4.2B transaction-volume figure is uncited and contradicts SDF's own reported figure of roughly $30M by two orders of magnitude. The SDF's ~30B XLM holdings figure is sourced to an article that doesn't actually establish current-state holdings and conflicts with more recent (if lower-quality) secondary reporting. The bug bounty program description (Immunefi + HackerOne) is now stale following a May 2026 consolidation onto HackerOne. The 'fake hard fork campaigns' claim is not supported by its cited source, which documents airdrop-themed phishing instead. The BlackWallet timeline date is off by two days (reflects article publication date, not incident date). Market cap/rank figures in the summary are an inherently moving target and uncited.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}