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
#3
Score
55 → 55 (0)
Cluster
mainnet-beta
Slot
464460109
Off-chain at
2026-11-02T10:22:32.581Z
Anchored at
2026-11-02T10:22:33.000Z
Block time
2026-11-02T10:22:33.000Z

Independent verification

1. Database (off-chain)
FsnAGbhWTtKHzHhwo2j4Q3wtNonLGdMX6T8jtCZFU2RG
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1258 chars)
{"actor":"reviewer","artifact_identity":"519b50367eaa0830ecdb1779748ae949","blocked_count":2,"decided_at":"2026-11-02T10:22:32.511Z","decision":"review","disputed_pct":0.3333,"findings_hash":"GZeqHfaNxkJvXrF7tAj3NY7AEz7GgcJu5EvE57KkFh9r","investigation_id":"bdadc939-db8a-469e-9f90-efc0aa2e2810","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_content_hash":"7c606ec38d5391fbc103d6a45e273e974756bb47328bac7c332d9deb9e6802af","page_slug":"astrid-finance","prev_score":55,"reason":"The core exploit facts (date, attacker address, tx hash, mechanism, ~127 ETH loss, 80% return and deadline) match independent reporting. Several cited sources returned 403, so the per-token figures and the audit-retraction detail could not be verified. The ZachXBT section is stated as fact but unsupported by any source, and the page itself says it could not be verified. No shutdown or relaunch was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}