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 · BlazeStake
- Sequence
- #2
- Score
- 72 → 72 (0)
- Cluster
- mainnet-beta
- Slot
- 423482133
- Off-chain at
- 2026-06-01T00:21:11.431Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7kMKkQntGMTYYfDGomUxEmev4my8QiUFWYYU5kAVSDZN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1288 chars)
{"actor":"reviewer","decided_at":"2026-06-01T00:21:11.212Z","decision":"review","investigation_id":"3b11ad47-fb22-4e94-8358-15986f869130","new_score":72,"page_slug":"blazestake","prev_score":72,"reason":"The BlazeStake investigation is largely accurate and well-sourced. The most significant factual error is a recurring undercount of the spl-stake-pool audit total: the page states 'seven audits from five firms' throughout, but the official BlazeStake audits page and the anza-xyz security audits repository list eight audits. A secondary but notable issue is that the $155 million MarginFi single-day outflow claim overstates what is confirmed as a single-day figure (CoinDesk cites $80-100M on the resignation day; $155M is the multi-day net outflow). The Pavlovsky resignation date is one day off (April 10 vs April 11). The $278M TVL December 2023 claim cites a source that contains no TVL data. All other core claims — launch date, protocol mechanism, Custom Liquid Staking debut, validator distribution statistics, team pseudonymity, multisig governance, and the MarginFi dispute narrative — are confirmed by independent credible sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}