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 · Hinkal Protocol
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 443511819
- Off-chain at
- 2026-08-25T04:06:36.783Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- C138KB3KJCH4qxW7DcymhWmDp2v7v5qfySxXFYnXZpas
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1324 chars)
{"actor":"reviewer","decided_at":"2026-08-25T04:06:36.562Z","decision":"review","investigation_id":"fdf124d2-1bbf-496e-bfd8-259013dd6bbf","new_score":28,"page_slug":"hinkal-protocol","prev_score":28,"reason":"The page's core narrative -- a nullifier-binding double-spend flaw in Hinkal's legacy note format drained roughly $800K in USDC on July 3, 2026, followed by Tornado Cash/THORChain laundering, a contract pause, and a 1:1 reimbursement pledge -- is well supported by its cited sources and independent corroboration. The main weaknesses are: an undisclosed spread in the total-loss figure ($772K-$830K across the page's own cited outlets, one of which explicitly frames $797K as a downward revision of the $820K figure the page uses throughout); a simplified description of the exploit's transaction pattern that does not fully match the page's own primary technical source; an unsourced $500M cumulative-volume figure traceable only to the protocol's own marketing; an incomplete funding history that omits an earlier, larger seed round; and a 'current status' framing that appears to predate a July 20, 2026 reimbursement-process announcement found via independent research.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}