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 · Citrine Sleet / AppleJeus
- Sequence
- #3
- Score
- 0 → 0 (-3)
- Cluster
- mainnet-beta
- Slot
- 426291166
- Off-chain at
- 2026-06-13T22:39:06.377Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 38m11vnHfvGxLb1mJTVudbyny26DTepuwqSZhRLzf5c5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1210 chars)
{"actor":"judge","decided_at":"2026-06-13T22:39:06.206Z","decision":"review_approve","investigation_id":"6756abb1-fffe-4beb-a1de-ea0c3f432d07","new_score":0,"page_slug":"citrine-sleet-applejeus","prev_score":0,"reason":"The review confirmed 20 of 27 claims outright, with 5 partially supported and only 1 disputed, yielding a disputed_pct of 7.4% — within the 0-10% approve band. The single disputed claim (claim_findings[12]) is a verifiable factual error: the page states CVE-2024-7971 carries a CVSS score of 8.8, whereas NVD and multiple Tier 1 CVE databases assign 9.6. Additionally, claim_findings[9] overstates Mandiant's published confidence — Mandiant assessed moderate confidence that UNC4736 specifically caused the 3CX compromise, not high confidence. These are correctable factual details, not fabrications or core attribution errors. All primary attributions, technical indicators, and financial figures are well-sourced from Tier 1 and Tier 2 authorities. Coverage gaps are medium or low priority and suggest expansion rather than accuracy remediation.","score_delta":-3,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}