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 · Makina Finance
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 462188048
- Off-chain at
- 2026-10-27T19:24:25.288Z
- Anchored at
- 2026-10-27T19:24:59.000Z
- Block time
- 2026-10-27T19:24:59.000Z
Independent verification
- 1. Database (off-chain)
- C9R9jSNywZ87tC7tjRLpbnxi9UZedbRpf3vsjCjnP59h
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1339 chars)
{"actor":"reviewer","artifact_identity":"b8c141856861dc731b4f42a1bd2e8c55","blocked_count":1,"decided_at":"2026-10-27T19:24:25.118Z","decision":"review","disputed_pct":0.1,"findings_hash":"Gnb6C7sc3gQCr4wNDhJ627SPjfKktPqdJTnSYoTkZGzx","investigation_id":"c25b7ed2-b6ed-408c-a13a-d20999d0edd3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_content_hash":"2f9a7635dce796d0b47258dea232a5005c5e97f82e887d78b95c258e9dbaf976","page_slug":"makina","prev_score":52,"reason":"The core incident narrative (exploit date, about 1,299 ETH / $4.13M, 280M USDC flash loans, six audits, the Cantina exclusion, v1.1 hardening, KYC terms) matches Rekt, Cryptopolitan and the official reactivation post. Two issues stand out. The 1,023 ETH figure for the 0xbed2 address differs from Rekt's 1,062 ETH. The headline $3.65M recovered / 89% / restitution plan claim, also in the summary, is not supported by any source read. Subject appears to be operating; no critical omissions found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}