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
- #5
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 462356400
- Off-chain at
- 2026-10-28T05:22:23.732Z
- Anchored at
- 2026-10-28T05:22:44.000Z
- Block time
- 2026-10-28T05:22:44.000Z
Independent verification
- 1. Database (off-chain)
- 9htt5rkKEcjRJ5TWBheYCgEMEEa6TGejyRsf69jVf6Xq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2129 chars)
{"actor":"reviewer","artifact_identity":"0b7c8f9458dc176253f20234d4c5f4c5","decided_at":"2026-10-28T05:22:23.548Z","decision":"review","disputed_pct":0.0556,"findings_hash":"1E6tJNJXZM5bAQUAE1eftZuM55aFh7wbAsid6uLak73","investigation_id":"54a8ddaf-9849-484f-8c3a-7d1657adcfa2","mode":"findings_only","new_score":50,"omissions":{"material":1,"total":2},"page_content_hash":"899516884fb0f19c3454ebd678cd44b52c4f508e66950a410c712bbc74c3a16c","page_slug":"forcebridge","prev_score":50,"reason":"The page's core narrative — ForceBridge's October 2021 launch, Magickbase's May/June 2025 sunset announcement, the June 2, 2025 exploit (access-control failure, ~$3.7-3.9M stolen, Tornado Cash/FixedFloat laundering), Magickbase's public response, and the absence of regulatory action — is well supported by independently fetched, mostly reputable sources (The Block, Halborn, okx.com, crypto.news, mpost.io, sunset.forcebridge.com). Specific figures (asset amounts, UTC timestamps, loss ranges) were verified essentially exactly against tier-1/tier-2 sources. Two issues stand out: the timeline's claim that Cardano and Polkadot connectivity went live at the October 2021 launch is contradicted by the page's own cited launch-era sources, which describe those chains as 'coming soon' at the time; and there is an unresolved one-day discrepancy between the page's May 31, 2025 sunset-announcement date and the sunset site's own June 1, 2025 timeline entry, which the page's own 'one day after' framing of the exploit actually fits better if June 1 is correct. Neither issue is severe, but both should be corrected or caveated. No material omissions beyond minor currency-of-information points were found; the project's current shut-down/exploited status is accurately reflected in the page's own 'Protocol Sunset and Current Status' section.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}