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.
- Sequence
- #3
- Score
- 29 → 29 (0)
- Cluster
- mainnet-beta
- Slot
- 463286048
- Off-chain at
- 2026-10-30T12:31:24.130Z
- Anchored at
- 2026-10-30T12:31:31.000Z
- Block time
- 2026-10-30T12:31:31.000Z
Independent verification
- 1. Database (off-chain)
- HcFgEvz8vdt6oAcgWuuqdZ5HvfXX8csr4YLrWABaXixP
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1342 chars)
{"actor":"reviewer","artifact_identity":"dbbc8b91df076eafa6e9f84ae1e50f6c","decided_at":"2026-10-30T12:31:24.076Z","decision":"review","disputed_pct":0,"findings_hash":"31MkumtmssDKhsEfzgvktWjgiXzFP2zRywjD9yEVY5H1","investigation_id":"2eb38693-7b58-462d-9a08-8698c50e40b4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":29,"omissions":{"material":1,"total":1},"page_content_hash":"c8f3143be4c4d81492dcf0f270f1417bd0036828040d6d003ce8e107edfba754","page_slug":"symbiosis-finance-bridgev2-sybtc-exploit-september-2026","prev_score":29,"reason":"Core facts hold up against KuCoin and CoinDesk: the 330-sat deposit, 12 transactions, 46.1B syBTC minted, 9.97 BTC (~$770K) preliminary loss, ~$336K realised, ~15 BTC recovered, and the bounty. The page is stale on the post-mortem: CoinDesk reports one was published Sept 15, and it supports the two-bug root cause over the page's competing account. Two archive URLs point to unrelated articles. Several secondary claims were not independently checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}