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 · Maestro
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425426671
- Off-chain at
- 2026-06-09T23:23:03.359Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 65F4tog7WeP8Y3CDqUJVfaBDac1Q3DF3cuazJG7thZsr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (971 chars)
{"actor":"reviewer","decided_at":"2026-06-09T23:23:03.286Z","decision":"review","investigation_id":"ff789ca3-84dc-4005-a82d-1ceedff98435","new_score":52,"page_slug":"maestro","prev_score":52,"reason":"The investigation page's core factual claims about the October 2023 exploit, refund, company identity, and custody model are well-supported by credible sources. The main weaknesses are: the '14 blockchains' figure contradicts the current official website (10 chains); the November 6 refund completion date conflates the press release date with the actual refund completion; the docs.maestrobots.com/faq/security URL cited for the custody model has link rot (404); and several timeline dates use January 1 or November 1 placeholders that are not supported by any source. No claims are outright disputed by more credible evidence.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}