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 · PiggyBank Protocol
- Sequence
- #3
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 425571478
- Off-chain at
- 2026-06-10T15:19:10.911Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8Xye872AuGWBbELEA8i7ZGkMq5omar3o4rffoTm4UwwA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1067 chars)
{"actor":"judge","decided_at":"2026-06-10T15:19:10.638Z","decision":"review_approve","investigation_id":"4832d100-6f44-4d70-a8be-ebdc596fc278","new_score":32,"page_slug":"piggybank-protocol","prev_score":32,"reason":"The reviewer checked 24 claims and found zero disputed. Twenty claims were fully confirmed by independent sources, three are partially supported due to minor wording imprecision (claim_findings[2] on epoch timing, claim_findings[4] on Formal Land's relationship to Nomadic Labs, claim_findings[3] on USDC vault specifics), and one is unverifiable from available public sources. The disputed_pct of 4.2% falls well within the 0-10% approval band. Three high-priority coverage gaps remain open — on-chain verification of the LAB position, audit PDF scope, and LAB supply concentration — but these call for page expansion rather than correction, and do not undermine the accuracy of what is currently published.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}