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
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 443524815
- Off-chain at
- 2026-08-27T08:08:52.936Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Cq3DA3xFKZvNxi7aNxNRKN3vrS6VncANVRBBPuDxQvc7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1430 chars)
{"actor":"reviewer","decided_at":"2026-08-27T08:08:52.725Z","decision":"review","investigation_id":"c2e1e834-593f-44ff-8d7f-fda4a68fcbc3","new_score":52,"page_slug":"zcash-orchard-pool-counterfeiting-vulnerability","prev_score":52,"reason":"The page correctly identifies this as a 2022-2026 Orchard-pool soundness bug distinct from the earlier 2018/2019 Sprout counterfeiting vulnerability, and it appropriately hedges the 'was it exploited' question rather than falsely certifying an absence of exploitation, consistent with Shielded Labs' own careful language. However, the page consistently misdates public disclosure as June 5, 2026, when the vulnerability's own disclosing entity (Shielded Labs) and two independent outlets (The Block, Gizmodo) date disclosure to June 4, 2026 — a discrepancy that recurs in the summary, two sections, and multiple timeline entries. The page also overstates what the turnstile mechanism proves about supply integrity in one section in a way that contradicts its own more careful hedging elsewhere, gets the historical NU5/Orchard activation date wrong by 30 days in the timeline, and includes several specific figures (a zebrad version cutoff, a $330 stabilization price, a Shielded Labs hiring announcement) that could not be independently verified.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}