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 · Maestro
- Sequence
- #3
- Score
- 52 → 47 (-5)
- Cluster
- mainnet-beta
- Slot
- 425426675
- Off-chain at
- 2026-06-09T23:23:03.458Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7dCpAJzN9pCfPZXti3Na4qVNgMhoDRYKD5T1dXkk94yL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1200 chars)
{"actor":"judge","decided_at":"2026-06-09T23:23:03.286Z","decision":"review_approve","investigation_id":"ff789ca3-84dc-4005-a82d-1ceedff98435","new_score":47,"page_slug":"maestro","prev_score":52,"reason":"The review found 0 disputed claims out of 16 (disputed_pct 6.25%), placing this page in the approve band. Nine claims are fully confirmed by Tier 1 and Tier 2 sources, including all core exploit facts (claim_findings[2], [3], [4], [10], [11], [12], [13]). Six claims are partially supported but not contradicted: notably, the '14 blockchains' figure in claim_findings[1] is contradicted by the official Maestro website (10 chains), and the refund timeline in claim_findings[14] conflates the November 6 press release date with the actual completion window. One citation has link rot (docs.maestrobots.com/faq/security, claim_findings[5]). A modest score adjustment of -5 reflects these inaccuracies. Two high-priority coverage gaps (on-chain transaction verification, acquisition details) suggest the page warrants expansion but do not justify denial.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}