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_revise · ForceBridge
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 461976247
- Off-chain at
- 2026-10-27T06:53:37.815Z
- Anchored at
- 2026-10-27T06:54:13.000Z
- Block time
- 2026-10-27T06:54:13.000Z
Independent verification
- 1. Database (off-chain)
- pk7vACk1qWk5dGGBd7VEvwSA7Q4PaTC49WfjiwBBVcK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1257 chars)
{"actor":"judge","artifact_identity":"ff4f68d88008f308c7863058d39e7495","band_override":null,"decided_at":"2026-10-27T06:53:37.405Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"54a8ddaf-9849-484f-8c3a-7d1657adcfa2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"forcebridge","prev_score":50,"reason":"Of 12 claims checked, none were contradicted, but 3 could not be verified (claim_findings[2], [10], [11]), giving a 25% unverified share. The core incident, loss amounts, asset breakdown, laundering route, sunset dates and team response were confirmed by multiple sources and the official sunset page. The page also states two inferences more firmly than sources allow: the compromised-key cause (claim_findings[1]) and the 'systemic operational security failure' conclusion (claim_findings[8]). The one omission, post-January 2026 withdrawal status, is minor, and the page already covers the shutdown and exploit.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}