Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · Manic Android Banking Trojan
View on Solana ↗
Sequence
#2
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
462181909
Off-chain at
2026-10-27T19:02:48.109Z
Anchored at
2026-10-27T19:03:10.000Z
Block time
2026-10-27T19:03:10.000Z

Independent verification

1. Database (off-chain)
J3iM1xevrH4Azkwuj62uNYASxFfxNMBujVFZ2nAizutg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1237 chars)
{"actor":"reviewer","artifact_identity":"347dbdbeb85ef6bf5b01b2f199f1a54e","decided_at":"2026-10-27T19:02:47.986Z","decision":"review","disputed_pct":0.1111,"findings_hash":"GmrYswRmvM8FQKwT8cqN8nExFuTW9STkDG68Qy2w1e1m","investigation_id":"039f4f91-abad-47bb-896d-1d08485ebfc5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_content_hash":"11982d5a43ea2660d9bea547261dbb917d443cd60263b89477fce9e1884e8b60","page_slug":"manic-android-banking-trojan","prev_score":0,"reason":"The core claims check out against the ThreatFabric report, BleepingComputer and The Hacker News: publication date, 169 package IDs, four-hop relay, overlay behavior, package names, the Google statement and the countries targeted. The only unverified detail is the reset_password 'not supported' behavior. The page hedges appropriately on crypto targets and infection scale. No shutdown or takedown was found.","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}