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
- #7
- Score
- 4 → 4 (0)
- Cluster
- mainnet-beta
- Slot
- 470633424
- Off-chain at
- 2026-11-17T18:25:09.770Z
- Anchored at
- 2026-11-17T18:25:25.000Z
- Block time
- 2026-11-17T18:25:25.000Z
Independent verification
- 1. Database (off-chain)
- EiSUK2SVXwfFZtAG3vD9sgBgPAZk38r34VLjTyhbjT1s
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1180 chars)
{"actor":"reviewer","artifact_identity":"35d64d79f4a76bd009c92df72b299b38","decided_at":"2026-11-17T18:25:09.598Z","decision":"review","disputed_pct":0,"findings_hash":"6t6zhDndLLDcuxG9pXP71RmHQPiF6c5x48fcsZQ31y9H","investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":4,"page_content_hash":"db913d62aa4b37e325a32ba1542b3cbfd550b4c1d77fed33d753c4de744ef7cc","page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":4,"reason":"The page's claims match the two main sources (CryptoSlate and ForkLog) closely and hedge appropriately on unverified figures and the lack of a SingularityNET statement. The only issues are two timeline dates given at month precision that the sources support at day level. A web search found no later developments that contradict the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":7,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}