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_revise · Sapphire Sleet / UNC1069
- Sequence
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464374965
- Off-chain at
- 2026-11-02T05:18:18.424Z
- Anchored at
- 2026-11-02T05:18:49.000Z
- Block time
- 2026-11-02T05:18:49.000Z
Independent verification
- 1. Database (off-chain)
- DCvT7pLMSEqwAsc47U7Kx48YSvtko1KFfWKZewkioJQs
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1459 chars)
{"actor":"judge","artifact_identity":"32dcc9e324f8dec1da29ddbcae7b8116","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T05:18:18.179Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"b6254be6-dc3f-47ad-9b36-ca3a0500fe88","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"sapphire-sleet-unc1069","prev_score":0,"reason":"The core attribution of the March 2026 axios compromise to Sapphire Sleet/UNC1069 is supported by Microsoft and Google reporting (claim_findings[4], claim_findings[6]). However, about 43% of the scorable claims (3 of 7, with one blocked claim excluded) were disputed or could not be found in the cited sources: the C2 URL path differs from Microsoft's (claim_findings[5]), and the credential list and the install count and timestamps are credited to a CISA alert that does not contain them (claim_findings[1], claim_findings[2]). Two further items are partly supported: the March 2020 date and the April 2 attribution date (claim_findings[0], claim_findings[3]). The review is partial and its confidence is moderate, so the penalty is kept at the lower end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}