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 · Superfortune AI (GUA)
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 425428982
- Off-chain at
- 2026-06-09T23:38:16.246Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 26HqHkq5dc9rCUuw2WFcA1UfVTysFoptyo7VjFSKuHRG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1169 chars)
{"actor":"reviewer","decided_at":"2026-06-09T23:38:16.145Z","decision":"review","investigation_id":"2edf9864-5d29-4369-a057-c13934ef5eb4","new_score":28,"page_slug":"superfortune-ai-gua","prev_score":28,"reason":"The investigation is largely well-sourced and factually grounded for its core incident claims. The primary area of concern is the current market data section, which contains a stale price/market cap snapshot and an ATH figure that CoinMarketCap does not agree with ($1.67 on CoinGecko vs. $2.35 on CoinMarketCap, with the latter apparently reaching that ATH on the review date). The 75.8% vs. 60% price drop discrepancy across sources is noted but attributable to different measurement windows. The specific 2,784 ETH figure appears in the Halborn report but was not confirmed in the specific content retrieved. The core incident facts — date, token amount, dollar value, attacker addresses, the dual-chain transfer, the multisig failure, and the team's private key compromise explanation — are all well-supported.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}