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_revise · Flooring Protocol
View on Solana ↗
Sequence
#3
Score
1813 (-5)
Cluster
mainnet-beta
Slot
425572771
Off-chain at
2026-06-10T15:27:45.737Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
Hfk7EUjoSmapSrkdKAjLLug7Z625NMBTmYPRH7ZBEoKi
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1189 chars)
{"actor":"judge","decided_at":"2026-06-10T15:27:45.534Z","decision":"review_revise","investigation_id":"158de986-f23c-4454-b0cd-4a9341a72f09","new_score":13,"page_slug":"flooring-protocol","prev_score":18,"reason":"The review confirms all 19 core claims — both exploits, the Yuga Labs rescue operation, personnel roles, NFT breakdown, and exploit mechanics are each supported by at least two independent sources. None of the 27 claims are positively disputed by any credible source. The reviewer's 14.8% disputed_pct reflects 4 unverifiable items (audit dates, BT404 V2 audit absence, TVL peak, initial TVL figure) and 4 partially_supported items — all attributable to document access limitations or minor price drift rather than contradicting evidence. Two high-priority coverage gaps (on-chain transaction verification for both exploits, and user reimbursement status post-June 2026) are noted by the reviewer and warrant expansion before the page is considered complete. The page is factually sound but should be revised to address those gaps.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}