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 · Satori Finance
- Sequence
- #4
- Score
- 48 → 33 (-15)
- Cluster
- mainnet-beta
- Slot
- 461770101
- Off-chain at
- 2026-10-26T18:43:03.916Z
- Anchored at
- 2026-10-26T18:43:36.000Z
- Block time
- 2026-10-26T18:43:36.000Z
Independent verification
- 1. Database (off-chain)
- pWr28pnaRw53YtMrpMRABiuj5nZYU1PYgxtSYCMHyrr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2245 chars)
{"actor":"judge","artifact_identity":"a51b4badef0f43095e17f38422eec72e","band_override":null,"blocked_count":2,"decided_at":"2026-10-26T18:43:03.492Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1111,"investigation_id":"f006c427-cff1-4293-bc02-c0144dfc2169","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":33,"page_slug":"satori-finance","prev_score":48,"reason":"Of 11 claim findings, 2 were unverifiable only because the source blocked the reviewer (claim_findings[6] and [9]) and are left out of the count; of the remaining 9, one (claim_findings[8], the founding year and founder details) could not be verified, giving about 11% disputed or unverifiable. The core facts are confirmed by Tier 2 outlets: the May 2022 seed, the June 16, 2026 announcement, the July 16 deadline, and the volume, TVL and open-interest figures. The page is out of date, though. It is written as if the withdrawal deadline were still ahead (subject_status.contradicts_page, omission_findings[0]) and a high-priority coverage gap asks for post-deadline status. There are also smaller wording problems: the 'Ethereum-compatible' withdrawal claim is broader than its source (claim_findings[5]), and the mainnet month is unsupported (claim_findings[7]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"scored_claims":9,"sequence_num":4,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"The review reports a material omission and contradicts_page=true: the July 16, 2026 withdrawal deadline passed more than three months ago, but the page still says users 'have until' that date and should 'act immediately', and it does not say what happened afterward. The percentage alone (1 of 9 counted findings, about 11%) would sit at the bottom of the minor band, so the verdict is held at the minor band and pushed to the harsh end of it. The shutdown itself is already stated on the page and the underlying facts are confirmed, so a significant band and an investigation status change are not warranted."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}