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 · Abracadabra Finance (MIM Stablecoin)
- Sequence
- #5
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 464444280
- Off-chain at
- 2026-11-02T09:25:48.267Z
- Anchored at
- 2026-11-02T09:26:02.000Z
- Block time
- 2026-11-02T09:26:02.000Z
Independent verification
- 1. Database (off-chain)
- 4NcBbb4ekt1ignb6CaeksFYgRiubSpz7Ecib25C6oJxy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1946 chars)
{"actor":"judge","artifact_identity":"5343ccef546b449fe1e2337acdf29574","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T09:25:48.032Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"d12991a8-c2e7-480b-a4a5-e128b6666999","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"page_slug":"abracadabra-finance-mim-stablecoin","prev_score":35,"reason":"Scored claims show a modest dispute rate: claim_findings[0] gives an exploit count of four where the page body and The Block say three, and claim_findings[5] (market cap) could not be found in its cited source. The larger problem is that the page is out of date. claim_findings[1] and [2] are stale because MIM fell to about $0.50 on June 24-25, 2026 and the SPELL incentives were suspended, and the review reports a proposed protocol and MIM shutdown in September 2026 that the page does not mention. Because of these critical omissions the page is judged in the significant band, and the shutdown proposal's vote outcome remains unconfirmed. One finding was not scored because the source blocked the reviewer.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"Claim percentage (about 22%, 2 of 9 scored claims) implies the minor band, but omission_findings[0] (June 24-25, 2026 collapse to about $0.50, incentives suspended, Tier 1 source) and omission_findings[1] (reported September 2026 shutdown proposal) are critical, and subject_status.contradicts_page is true. The shutdown is reported by a single secondary outlet with the vote unconfirmed, so the band is raised to significant rather than deny."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}