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
- #3
- Score
- 20 → 0 (-20)
- Cluster
- mainnet-beta
- Slot
- 464359273
- Off-chain at
- 2026-11-02T04:22:12.937Z
- Anchored at
- 2026-11-02T04:22:42.000Z
- Block time
- 2026-11-02T04:22:42.000Z
Independent verification
- 1. Database (off-chain)
- FLj3V4LCkKigpAyEtG2tAbuN3atEAAzHdpFswBFnVMT1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1835 chars)
{"actor":"judge","artifact_identity":"672188af5b6a0fb03aece9f3def2ec41","band_override":null,"decided_at":"2026-11-02T04:22:12.663Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4375,"investigation_id":"78e21ab8-0078-481e-929f-fe389239af72","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"philippines-sec-multi-exchange-unlicensed-operations-enforcement","prev_score":20,"reason":"About 41% of the checked claims (7 of 17) were disputed or could not be verified, which falls in the significant-issues band. claim_findings[0] places the earlier ten exchanges on the December 2025 BSP list, which the cited source does not support. claim_findings[8] and [9] give the SEC defence date as Aug 29 when it was an Aug 27 webinar. claim_findings[13] shows the 'largest blocking' claim is contradicted by the page's own 50-platform entry. The core August 2025 story is supported, but the page stops at December 2025 and omits later enforcement, and several figures (penalties, capital, user numbers) remain unverified. The reviewer's confidence was moderate (0.5), so the penalty sits in the lower half of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-20,"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (nothing after December 2025, including continued enforcement and Bybit's 2026 withdrawal from the Philippines) and subject_status.contradicts_page is true. The percentage band is already significant, so the override holds that band and does not move it to a more lenient one."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}