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
- Sequence
- #4
- Score
- 40 → 40 (0)
- Cluster
- mainnet-beta
- Slot
- 462279165
- Off-chain at
- 2026-10-28T00:48:09.003Z
- Anchored at
- 2026-10-28T00:48:42.000Z
- Block time
- 2026-10-28T00:48:42.000Z
Independent verification
- 1. Database (off-chain)
- EfvwobgEoJiEHfdxcNSHmS5HuJu4oobTU3HRHJ6aAi8g
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2094 chars)
{"actor":"judge","artifact_identity":"7aad118a21e0c5c10932a0dca2098fe7","band_override":null,"decided_at":"2026-10-28T00:48:08.724Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"1465afad-ef3f-4492-a4ba-e2cc1bb44102","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":40,"page_slug":"bitmart-exchange-creditor-committee-september-9-roadmap-deadline-missed","prev_score":40,"reason":"Most dated facts check out against Tier 1 and Tier 2 sources: the July 26 wind-down, the Echo Base proposal and committee, the September 9 missed deadline and Alvarez and Marsal appointment, and the on-chain wallet figures. However, the claim that more than 12 million users are unable to withdraw is overstated (claim_findings[1], [2] and [12]), because CoinDesk reports withdrawals remain open with extra checks. The August 19 'user committee' and 'no public response' framing is also unsupported (claim_findings[6]). omission_findings[0] is critical: BitMart acknowledged an asset shortfall and proposed a settlement plan on September 30, which contradicts the page's statement that no asset information or path forward exists, and the 2021 hack is not mentioned at all. About 14% of claims were unverifiable, and the review also lists a high-priority coverage gap on post-September 16 developments.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"The review reports a critical omission (BitMart's September 30, 2026 shortfall admission and settlement proposal) and marks the page as contradicted by current subject status. The page's central theme is that BitMart has given no asset figures or path forward. The claim-level rate alone (2 of 14 unverifiable, 14%) falls in the minor band and understates this, so the significant band is applied."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}