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
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 461970867
- Off-chain at
- 2026-10-27T06:34:46.610Z
- Anchored at
- 2026-10-27T06:35:09.000Z
- Block time
- 2026-10-27T06:35:09.000Z
Independent verification
- 1. Database (off-chain)
- V2KvpiAP7RnXeMruEqkj1989pdYswDWptDsTiKWEMgY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1494 chars)
{"actor":"reviewer","artifact_identity":"312e9989ee1a1389ff21f0301a047840","decided_at":"2026-10-27T06:34:46.274Z","decision":"review","disputed_pct":0.0833,"findings_hash":"Exrwyv4ZqBqFBhS9L9qkBPC1P2i6Gbx9kb9pb82DJZeR","investigation_id":"f148389b-fbdf-4f1b-9c26-b291f88ef903","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":38,"omissions":{"material":1,"total":2},"page_content_hash":"5c248f775cff05ed2ff770df6e8a0a1c105984fe3773ea071fbe95dd93c54a26","page_slug":"bitget-exchange-september-2026-backend-hack-387-5m","prev_score":38,"reason":"The core narrative holds: $351.6M revised to $387.5M, backend spoofing rather than key theft, suspected DPRK involvement, NEAR Intents and stablecoin freezes, THORChain refusal, the phased reopening and the $464M fund are all corroborated. Weak points are the unsourced '19 unauthorized withdrawals', cold-wallet safety stated as fact despite a conflicting on-chain analysis, an inexact THORChain quotation, two ZachXBT aliases not verified, and a CoinCentral archive link that points to an unrelated article. The page omits the later third-party-product root cause and the large post-reopening outflows.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}