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
- 20 → 20 (0)
- Cluster
- mainnet-beta
- Slot
- 464359267
- Off-chain at
- 2026-11-02T04:22:12.723Z
- Anchored at
- 2026-11-02T04:22:41.000Z
- Block time
- 2026-11-02T04:22:41.000Z
Independent verification
- 1. Database (off-chain)
- EfsmfjRJzDVE71mKXKRnXF9mb9UZbtRbWVgzNZVnePQt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1503 chars)
{"actor":"reviewer","artifact_identity":"672188af5b6a0fb03aece9f3def2ec41","decided_at":"2026-11-02T04:22:12.663Z","decision":"review","disputed_pct":0.4375,"findings_hash":"AiXN47skNwfnUKouXkLcSvw51rYDof56iSh2kKdxQozB","investigation_id":"78e21ab8-0078-481e-929f-fe389239af72","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":20,"omissions":{"material":1,"total":1},"page_content_hash":"5fdcbc5152e375846fc615ed65e385faa3354ed584f2f07d7d0a46b53d6c81a4","page_slug":"philippines-sec-multi-exchange-unlicensed-operations-enforcement","prev_score":20,"reason":"The core story (August 2025 SEC advisory, PLDT/Smart blocking, July 5 effectivity, exchange responses) is supported. Errors found: the December 2025 timeline entry claims the earlier ten exchanges were on the BSP list, which the cited source does not support; the Aug 29 SEC defence was actually a webinar on Aug 27; the advisory date is disputed between sources (Aug 1 vs Aug 4); the 'largest blocking' claim is superseded by the page's own 50-platform entry. Several claims (penalties, capital, user numbers, block page) could not be verified in the available time. The page stops at December 2025.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}