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 · ForceBridge
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 461976242
- Off-chain at
- 2026-10-27T06:53:37.646Z
- Anchored at
- 2026-10-27T06:54:12.000Z
- Block time
- 2026-10-27T06:54:12.000Z
Independent verification
- 1. Database (off-chain)
- AUMWu8DL2nVzHDEs8v782F6xaMbDifFym7kwai7hQD5g
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1415 chars)
{"actor":"reviewer","artifact_identity":"ff4f68d88008f308c7863058d39e7495","decided_at":"2026-10-27T06:53:37.405Z","decision":"review","disputed_pct":0.25,"findings_hash":"4bAJvvCT2PN58mqELEpbnpCyMxYKeumz5ymnwW8fz416","investigation_id":"54a8ddaf-9849-484f-8c3a-7d1657adcfa2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"omissions":{"material":0,"total":1},"page_content_hash":"899516884fb0f19c3454ebd678cd44b52c4f508e66950a410c712bbc74c3a16c","page_slug":"forcebridge","prev_score":50,"reason":"The core facts hold: the June 2025 access-control exploit, the loss of roughly $3.7-3.9M, laundering through Tornado Cash and FixedFloat, the asset breakdown, the sunset dates and the Magickbase response all match Halborn, Rekt, OKX/PANews and the official sunset page. Three weak spots remain. The $25 test drain and exact UTC timestamps are unsourced. The compromised-key cause is inference. The 'systemic operational security failure' conclusion is editorial. The exploit date also varies by a day across sources depending on timezone. No claims are contradicted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}