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 · Sapphire Sleet / UNC1069
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464374960
- Off-chain at
- 2026-11-02T05:18:18.237Z
- Anchored at
- 2026-11-02T05:18:48.000Z
- Block time
- 2026-11-02T05:18:48.000Z
Independent verification
- 1. Database (off-chain)
- BaLA5ZPdAqxQosn4Q8zXehmnw3pmdo11cfPm2gXzrWrR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1517 chars)
{"actor":"reviewer","artifact_identity":"32dcc9e324f8dec1da29ddbcae7b8116","blocked_count":1,"decided_at":"2026-11-02T05:18:18.179Z","decision":"review","disputed_pct":0.4286,"findings_hash":"DAm74kyq5S9TbhvgwGBy1tvtfYuahT6zSYMq917rMtbp","investigation_id":"b6254be6-dc3f-47ad-9b36-ca3a0500fe88","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"omissions":{"material":0,"total":1},"page_content_hash":"2c7652a30deef47e0c361e49bb6b23b67e067b8b46455e9ba95addfbbeb021d1","page_slug":"sapphire-sleet-unc1069","prev_score":0,"reason":"The core story holds: Microsoft and Google attribute the March 31, 2026 axios compromise to Sapphire Sleet/UNC1069, and the versions, C2 domain/IP, port, behavior and remediation match Microsoft and Unit 42. Problems: several claims are credited to CISA that its alert does not contain (attribution-free, no install count, no timestamps, no credential list, no file artifacts); the March 2020 Microsoft date is an activity date, not a tracking-start date; the April 2 Google attribution date is uncertain; and the C2 URL path differs from Microsoft's. Several secondary sources were not fetched, so the review is partial.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}