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 · Stellar
- Sequence
- #2
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 425011341
- Off-chain at
- 2026-06-08T01:28:30.489Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HXarfrDY5Nxi8iJsr5bVsDMCKHsLpwHuanET8FDVcATg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (899 chars)
{"actor":"reviewer","decided_at":"2026-06-08T01:28:30.355Z","decision":"review","investigation_id":"bf37a4c8-4dc0-4158-a207-b4f89b78ed95","new_score":62,"page_slug":"stellar-xlm","prev_score":62,"reason":"The investigation page is generally well-sourced and accurate on historical events (BlackWallet, XLM burn, Soroban post-mortem, Twitter compromise, Dixon testimony). Key weaknesses are: the market cap/rank is materially outdated, the SDF XLM holdings figure (30B) is stale by approximately 50% relative to current data (~16.66B), the MoneyGram $4.2B transaction volume figure appears to be a misattribution that cannot be confirmed, and the Cyberint phishing source returns a 403 error. The Immunefi bug bounty claim is also newly stale as of May 2026.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}