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_revise · StakeDAO
View on Solana ↗
Sequence
#3
Score
38 → 20 (-18)
Cluster
mainnet-beta
Slot
443519576
Off-chain at
2026-08-26T07:06:21.048Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
GggoTHj7LxVfGSkyQHuq7fgENj7K2W2WnMC6FpnLFyk7
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1723 chars)
{"actor":"judge","decided_at":"2026-08-26T07:06:20.831Z","decision":"review_revise","investigation_id":"e045ecc6-65b7-40c1-9c52-77ca12ab20a3","new_score":20,"page_slug":"stakedao","prev_score":38,"reason":"The core exploit reporting on this page holds up well: the deployer-key compromise, the LayerZero setPeer reconfiguration, the ~5.44 trillion vsdCRV mint, and the ~$91,000 extraction are all strongly corroborated, and the page correctly avoids overstating Curve Finance's role as anything more than a swap venue and warning party. The mechanical disputed rate is low (about 3.7%), but the substance is worse than that number suggests: the page still tells readers that StakeDAO has not published a post-mortem and that the compensation timeline for affected users is unresolved, when StakeDAO in fact published a post-mortem and completed compensation for 242 affected addresses by July 9, 2026 -- roughly seven weeks before this review. One of these claims is not merely outdated but directly contradicted by a source dated before the page's own stated cutoff. Because this leaves readers with a materially inaccurate impression of an unresponsive, non-transparent team on a question central to judging the protocol's trustworthiness, and because the page also omits current TVL and operating status while still making claims about current state, the page needs revision and a closer look before its transparency narrative can be treated as current. A misattributed quote and one dead secondary link add further reason to return it for updates rather than accept it as-is.","score_delta":-18,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}