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 · Sonne Finance
View on Solana ↗
Sequence
#2
Score
10 → 10 (0)
Cluster
mainnet-beta
Slot
426700987
Off-chain at
2026-06-15T19:50:05.695Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
aYaV8GdStZCKjodmf3s8epKgnQZJkKzBi2fbWa34eNa
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1061 chars)
{"actor":"reviewer","decided_at":"2026-06-15T19:50:05.578Z","decision":"review","investigation_id":"46071ba8-e931-4806-addc-c35517a188ae","new_score":10,"page_slug":"sonne-finance","prev_score":10,"reason":"The Sonne Finance page is substantively accurate. All major claims — exploit amount, date, mechanism, assets drained, SEAL intervention, token drop, bounty offer, and Tornado Cash transfer — are confirmed by multiple tier-1 sources. Two claims are partially supported: the specific '2.3 million SONNE votes' figure for SIP-15 cannot be independently verified, and the May 12 preparatory transaction date is corroborated only by CertiK. One cited URL (The Block) returned 403 due to bot protection, which may indicate access restriction rather than true link rot. A significant omission is that yAudit had pre-flagged this exact attack vector as a high finding, which is relevant to assessing protocol negligence.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}