Skip to main content
Sign in
← 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
#2
Score
00 (0)
Cluster
mainnet-beta
Slot
423150261
Off-chain at
2026-05-30T11:47:48.816Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
6stKpatmFjGxffz9E3RCaFBYDuNcqDzaAoTutakfR3fP
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1070 chars)
{"actor":"reviewer","decided_at":"2026-05-30T11:47:48.748Z","decision":"review","investigation_id":"58625252-4783-49c8-bbb5-d44243a2b444","new_score":0,"page_slug":"uniswap-google-ad-phishing-campaign-may-2026","prev_score":0,"reason":"The investigation page is substantially accurate and well-sourced. The SEAL Radar primary source (credibility tier 1) directly confirms the majority of technical, financial, and operational claims. The main area requiring attention is drainer tool attribution: the page attributes the May 2026 campaign to Inferno Drainer and Vanilla Drainer (drawn from SEAL's March 2026 report), while Protos and CoinGabbar specifically name 'AngelFerno' for the May 2026 @ika_xbt incident and broader campaign — a distinction the page does not address. The enumerated protocol targeting list also omits 1inch (4% per SEAL) while listing smaller targets. No claims were found to be disputed or unverifiable.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}