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_revise · Unibot
View on Solana ↗
Sequence
#10
Score
65 → 65 (0)
Cluster
mainnet-beta
Slot
464992059
Off-chain at
2026-11-03T18:01:25.577Z
Anchored at
2026-11-03T18:01:50.000Z
Block time
2026-11-03T18:01:50.000Z

Independent verification

1. Database (off-chain)
4MH6cnFparDu1xwfo3hyBhDSC298GeLZ5G3ku7Us8fxS
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1533 chars)
{"actor":"judge","artifact_identity":"ac5d8a98402c799efe54f024c3298892","band_override":null,"blocked_count":2,"decided_at":"2026-11-03T18:01:25.175Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"5908d54b-dd44-42e9-b102-da2fe84998b1","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":65,"page_slug":"unibot","prev_score":65,"reason":"Of 7 checkable claims, 1 was disputed (about 14%), which falls in the minor-issues band. claim_findings[0] shows the page attributes the 334 ETH, 20% boost and 610 ETH compensation figures, and the 'funded from Maestro's revenue' framing, to Unibot, when the cited Cointelegraph article attributes them to a separate bot, Maestrobots; Unibot's own reported payout cost was about $1.78M. Two further claims were only partly supported (the 25-32% price drop omits the 42.7% in the cited Cointelegraph article, and the router deployment date conflicts between outlets). The core exploit facts, the loss range and the reimbursement figures were confirmed, and no omission or status contradiction was found. Two of nine findings (about 22%) could not be checked because sources were blocked or not fetched, which limits coverage and is not a defect of the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":7,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}