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_revise · Chainflip TRON USDT Exploit (September 2026)
- Sequence
- #3
- Score
- 28 → 26 (-2)
- Cluster
- mainnet-beta
- Slot
- 462055327
- Off-chain at
- 2026-10-27T11:34:04.922Z
- Anchored at
- 2026-10-27T11:34:32.000Z
- Block time
- 2026-10-27T11:34:32.000Z
Independent verification
- 1. Database (off-chain)
- 6s95niHDCLi56B9bkf7faRMJz96smTPKRZhEHQk12Tud
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1514 chars)
{"actor":"judge","artifact_identity":"976e2d14dcdf8fbb91b9e8eca3cddacd","band_override":null,"decided_at":"2026-10-27T11:34:04.311Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"a9a2357c-017c-409e-a727-76dcfa1373b6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"chainflip-tron-usdt-exploit-september-2026","prev_score":28,"reason":"The core facts on this page (eight attempts, six unauthorized payouts totaling 736,442.17 USDT, the 115,654.41 USDT in-flight swap, the 2.2.13 patch, TRON excluded from the restart) were confirmed against Chainflip's incident report and GitHub release notes (claim_findings[0-2], [4]). One of six checked claims (about 17%) could not be verified: the 'first significant critical vault loss' wording was not found in the official post (claim_findings[3]). The Coin-Turk archive link points to an unrelated article (claim_findings[5]). A high-priority gap remains because the status is about a month old and a promised post-mortem and compensation update has not been checked, so the page gets a minor revision rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-2,"score_limit":{"applied":-2,"limited":true,"proposed":-7,"rule":"limited_no_second_opinion","second":null},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}