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.

Decision
review · Zoth Protocol
View on Solana ↗
Sequence
#2
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
423871402
Off-chain at
2026-06-02T19:18:13.342Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
7fqAJLMrJtqrCHkYFcs3ZhhrHshtUUnzmva7pJaP7ipf
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1246 chars)
{"actor":"reviewer","decided_at":"2026-06-02T19:18:13.235Z","decision":"review","investigation_id":"4a736de8-81d9-4b63-944d-32ddd8b0ff17","new_score":28,"page_slug":"zoth-protocol","prev_score":28,"reason":"The core technical facts of the March 21, 2025 exploit — amounts, addresses, swap routes, and timeline — are well-supported by multiple independent security research sources. The principal accuracy problems are: (1) the timeline entry dating the PR Newswire press release to April 1, 2025 when the cited source is dated May 9, 2025; (2) the unsubstantiated claim that the March 1 LTV vulnerability was flagged in a prior audit, which no cited or independently discoverable source supports; (3) three cited URLs that are inaccessible (CoinTelegraph 404, Bitget 403, BitcoinEthereumNews 403); and (4) the 'March 14-15 ChangeNOW funding' framing, which conflates the March 14 ETH funding event with the March 15 malicious contract deployment. The business model section contains several unverified regulatory jurisdiction claims (Panama, Luxembourg, UAE) that lack any cited third-party confirmation.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}