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
8 → 0 (-8)
Cluster
mainnet-beta
Slot
462185879
Off-chain at
2026-10-27T19:16:55.456Z
Anchored at
2026-10-27T19:17:15.000Z
Block time
2026-10-27T19:17:15.000Z

Independent verification

1. Database (off-chain)
75YHAPj3kQWnsi9J32zddmhDkgCMoCpaAhoGHNWRVN5m
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1562 chars)
{"actor":"judge","artifact_identity":"05cbd3b3dd79ba40630fad53cf78fc17","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:16:55.147Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"d77556bb-a35d-47e1-b5f8-bbbbf0184ae1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"skydao-premature-sync-exploit-september-2026","prev_score":8,"reason":"The core exploit facts (date, flash-loan size, reserve loss, net profit, 35% tax mechanics) were confirmed against the DeFiHackLabs proof-of-concept (claim_findings[0], [1], [2]), and none of the claims were disputed. Two of seven checkable claims could not be verified: the statement that the proof-of-concept lists a transaction hash and addresses (claim_findings[3]) and the editorial statement about low liquidity and no audit history, which cites no source (claim_findings[7]). One further claim was blocked by a 403 and is left out of the percentage as a coverage limit, not as a defect. This gives about 29% unverified, and the page also lacks the on-chain transaction hash and addresses (high-priority coverage gap), so minor revisions are warranted. The Nominis quote is presented as the report's wording when it is not (claim_findings[5]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}