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.

Sequence
#7
Score
22 → 22 (0)
Cluster
mainnet-beta
Slot
464989840
Off-chain at
2026-11-03T17:53:32.087Z
Anchored at
2026-11-03T17:53:56.000Z
Block time
2026-11-03T17:53:56.000Z

Independent verification

1. Database (off-chain)
3G1Su1bzCeX8VizJhmsejxkPtKmk4medRP4VeMcrDRPZ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1316 chars)
{"actor":"reviewer","artifact_identity":"9366f6c5579b816fbd35f81531dfd50c","decided_at":"2026-11-03T17:53:31.960Z","decision":"review","disputed_pct":0,"findings_hash":"73ANEfnDoGyPAgmrnMANprPghWNMToygqaossuvmZBtV","investigation_id":"c4c14081-8d50-49af-8b76-783b23252d59","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":22,"omissions":{"material":0,"total":1},"page_content_hash":"1f8c35db6d84a35d7c331ed32385b1fd9d44f44649ec364f95ff46215f42e0f9","page_slug":"b-network-bsquared-bitcoin-layer-2-staking-contract-exploit","prev_score":22,"reason":"The checked claims on the page match the cited secondary sources (edgeX, CoinGabbar, KuCoin/AmbCrypto snippets) and the page hedges its weak points well (insider angle, laundering details, Lookonchain attribution, the 44% figure). Minor attribution blur on analyst names and varying price-drop figures across outlets. Sourcing is entirely secondary, which the page itself admits. No contradicting current status was found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}