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 · Arcadia Finance v1
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 465087904
- Off-chain at
- 2026-11-03T23:43:54.889Z
- Anchored at
- 2026-11-03T23:44:10.000Z
- Block time
- 2026-11-03T23:44:10.000Z
Independent verification
- 1. Database (off-chain)
- d2sJBCNRBEFHYbcJKiuryN3P5XNZEEAzwwgXFZ3wdTc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1291 chars)
{"actor":"reviewer","artifact_identity":"d9022772490e915520e4c59f8d5fdf4c","blocked_count":2,"decided_at":"2026-11-03T23:43:54.832Z","decision":"review","disputed_pct":0.125,"findings_hash":"z8dCjkGSrWLx4uwSWN1rpbtMYby869yxtTf6heVr4Zk","investigation_id":"cba3a26a-3789-4b6c-9429-ca7d9dfd4a18","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"omissions":{"material":0,"total":1},"page_content_hash":"4883771aa39e7c4938b894e479c163fd715ce6bdded586f365f8fbde98d86b19","page_slug":"arcadia-v1","prev_score":50,"reason":"The core narrative (July 2023 reentrancy exploit of about $455K, pause, ultimatum, and the July 2025 v2 exploit on Base) is consistent with the sources I could read. One audit date is wrong (Renascence). The AAA 46% drop and the exact per-chain loss figures were not verified, because the Medium post-mortem was blocked with a 403. The ZachXBT section is tangential, and one sentence is editorial inference.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":8,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}