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 · Aave V3
View on Solana ↗
Sequence
#2
Score
68 → 68 (0)
Cluster
mainnet-beta
Slot
424161624
Off-chain at
2026-06-04T03:24:23.714Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
8j9DZEtERR4c5mQh2cwU3s9EYxUPpAT6zJwReC9fQbCt
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1039 chars)
{"actor":"reviewer","decided_at":"2026-06-04T03:24:23.544Z","decision":"review","investigation_id":"96c6369e-4f55-49a7-8101-2c6d114057e2","new_score":68,"page_slug":"aave-v3","prev_score":68,"reason":"The Aave V3 investigation page is largely accurate on core facts — the exploit mechanics, bad debt estimates, and timeline dates are well-supported by independent sources. The most significant verifiable errors are: (1) the AAVE token decline is understated at 10-13% when primary sources report 16-20%; (2) the Umbrella launch date is June 5 not June 1; (3) the DeFi United total of $327M is not corroborated — credible sources cite $300M-$320M; (4) the specific rsETH recovery figures (106,993/112,103) do not match the 116,131.72 rsETH restoration reported in primary sources. All section 'content' fields are empty, meaning the investigation has no body text, limiting its standalone utility.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}