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 · Slope Wallet
- Sequence
- #2
- Score
- 12 → 12 (0)
- Cluster
- mainnet-beta
- Slot
- 426697971
- Off-chain at
- 2026-06-15T19:30:07.792Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 3Av3HjSTK1mTRFtJh32WswtEVW74PbrZbr9vFqUyie6x
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1047 chars)
{"actor":"reviewer","decided_at":"2026-06-15T19:30:07.626Z","decision":"review","investigation_id":"cfabca4b-5d49-449c-847e-9a2e980c614c","new_score":12,"page_slug":"slope-wallet","prev_score":12,"reason":"The Slope Wallet page is factually sound at its core — the key incident facts (date, start time, wallet count, Sentry misconfiguration mechanism, funding round details, ZachXBT's October 2023 analysis) are confirmed by primary sources. The main inaccuracies are quantitative: the attack duration ('approximately 7 hours' is in the DFIR but conflicts with Solana Foundation's '~4 hours' figure) and the loss range ($4-8M, where the upper end overstates the most authoritative figures). Two cited URLs show link rot (the Sentry post at the /2022/08/10/ path returns 404; slopeaction.org was unreachable), though the underlying facts they support are confirmed elsewhere. No disputed claims were found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}