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 · Stake DAO
View on Solana ↗
Sequence
#6
Score
57 → 57 (0)
Cluster
mainnet-beta
Slot
457657867
Off-chain at
2026-10-16T13:41:31.223Z
Anchored at
2026-10-16T13:41:39.748Z
Block time
—

Independent verification

1. Database (off-chain)
BrWAmnb1SSigugcuJPiyVfEiCuf422ja7RGNciJVEpJd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1777 chars)
{"actor":"reviewer","artifact_identity":"b370d01ac8777d8f3bd9269bf0e3e3c8","decided_at":"2026-10-16T13:41:30.987Z","decision":"review","disputed_pct":0.35,"findings_hash":"DRZq3kF6HXWdC2ePZHzgUeTuuLuiBJvazJ3VXh67YSWH","investigation_id":"22690c77-993d-44f5-aa47-0b2304ade6c1","mode":"findings_only","new_score":57,"page_content_hash":"7dfcbacf077cb2a4709d291564e2bf839bd224f0e25019b298758d3138f9ed8f","page_slug":"stake-dao","prev_score":57,"reason":"The page's central narrative — three security incidents (Nov 2023 CAKE/BNB Chain, March 2026 Votemarket oracle, May 2026 vsdCRV deployer-key exploit) — is well supported by primary disclosures (GitHub security repo, gov.stakedao.org proposals/reports) and corroborated by multiple independent news outlets, and the tokenomics and audit-history sections match primary documentation precisely. The weakest area is historical SDT price data: the page's cited source (CoinGecko) actually shows a different all-time-high ($17.38 vs. claimed $16.63) and a much lower all-time-low ($0.01523 on Oct 28, 2022 vs. claimed $0.1750 on June 15, 2022), and the January 2024 price figure appears to conflate a December 2024 price level. A quote attributed to Manuel Aráoz is framed as reacting to the May 2026 exploit when reporting shows he posted it beforehand as a general statement. Two specific sub-claims in the March 2026 incident writeup (veCRV Round 234, a blocked second attempt) and the inclusion of Kelp DAO in a 'compromised operational keys' pattern could not be fully verified or were only partially supported. No accepted community submissions were present to independently evaluate.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}