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_approve · Apyx Finance
- Sequence
- #3
- Score
- 38 → 33 (-5)
- Cluster
- mainnet-beta
- Slot
- 425411135
- Off-chain at
- 2026-06-09T21:40:33.782Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- oNaAM9psihVFf44DdcEcg4qEReWxVgqrU6mtSQYHtoN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1512 chars)
{"actor":"judge","decided_at":"2026-06-09T21:40:33.412Z","decision":"review_approve","investigation_id":"9c0b3b9e-05da-4d77-a230-19cfa8df272d","new_score":33,"page_slug":"apyx-finance","prev_score":38,"reason":"The review found zero disputed claims across 30 assessed items, with 24 confirmed and 4 partially supported. The partially supported findings (claim_findings[3], [6], [22], [23]) are minor: the SATA allocation figure is slightly overstated relative to more granular data, the cooldown period has an internal inconsistency in official docs, and funding round figures are already flagged as low-confidence on the page itself. The principal concern is claim_findings[7], a specific $23.4 million per-year yield discrepancy attributed to 'one independent analysis' — the reviewer could not locate this figure in any cited article upon direct fetch, making it unverifiable. This unsourced accounting allegation sits in a high-severity section without the same hedging language the page applies to its funding figures, and should be sourced or removed before the next review cycle. The modest score penalty reflects this single unverified claim in an otherwise well-evidenced page. Three high-priority coverage gaps (on-chain reserve verification, redemption stress test, Strategy balance sheet analysis) are noted for expansion but do not affect factual accuracy.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}