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 · Rubic
View on Solana ↗
Sequence
#3
Score
63 → 63 (0)
Cluster
mainnet-beta
Slot
464365694
Off-chain at
2026-11-02T04:45:23.882Z
Anchored at
2026-11-02T04:45:39.000Z
Block time
2026-11-02T04:45:39.000Z

Independent verification

1. Database (off-chain)
W5qZAqpqK6Mo5rNQhWnJvVkUynN7qxNr64Xjmj7N8Dh
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1388 chars)
{"actor":"reviewer","artifact_identity":"6282d418755fe49db1cbd4182dae33ee","blocked_count":1,"decided_at":"2026-11-02T04:45:23.830Z","decision":"review","disputed_pct":0.2222,"findings_hash":"4jCXM1ADZ1Kn3j8Ya8YEyN8GTvfhsMPK9CSGv6yyz4WP","investigation_id":"88f93946-9f2c-4759-9f76-2b60c05315a3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":63,"page_content_hash":"6e567be376e9d16a8ef17ad0bc1666e5ebb1b1f1d0bda768b47429c1a89d2659","page_slug":"rubic","prev_score":63,"reason":"The core incident facts (Nov 2022 key compromise, Dec 2022 USDC exploit, Tornado Cash laundering, security overhaul, 2024 self-reported metrics) are supported by the sources I fetched. Weaker points are the compensation cap, personal-savings funding and 49-user figures, which the cited sources do not show, and the 2023 year of the April 3 relaunch, which the cited blog does not state. Not every claim was checked, including the DFintoch/ZachXBT section, the token economics and the Messari figures. No contradicting current status was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"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}