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
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 464279531
- Off-chain at
- 2026-11-01T23:37:50.233Z
- Anchored at
- 2026-11-01T23:37:59.000Z
- Block time
- 2026-11-01T23:37:59.000Z
Independent verification
- 1. Database (off-chain)
- 92GkMvxiTaJ7KLfsxk8a5Jsq9ZhSqaRqcWwLrs3FZCpT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1425 chars)
{"actor":"reviewer","artifact_identity":"9449a316aecea0bbc0412ec2ec527c1b","decided_at":"2026-11-01T23:37:50.161Z","decision":"review","disputed_pct":0.2308,"findings_hash":"AqNYmAsDDwBeUSedmAVt6Tdj1Ztqcq8uT2q38MqAf2cv","investigation_id":"b2d97eef-f3b5-4dcb-8128-ea66069d00b6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":22,"omissions":{"material":0,"total":1},"page_content_hash":"10c0b2a807fdc797d13c063636367afb1c22061e9636bb26ee0ada15e981b4d5","page_slug":"trezor-email-provider-breach-brevo-september-2026","prev_score":22,"reason":"The core facts (Sept 9 SSO abuse, 138 accounts, 6 phishing and 43 exported, about 347,149 recipients, about 2,500 clicks, 20-minute takedown, no reported losses) are supported by Trezor and Brevo primary sources. The page overstates that Brevo's permanent fix was deployed on Sept 10, when the write-up says it was being deployed. Several secondary details (hardcoded Cloudflare key, CVE number, exact Worker clock times, Mailchimp date) could not be confirmed from the sources I read. The page omits the 120 vs 138 account discrepancy.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}