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 · Sky (MakerDAO)
View on Solana ↗
Sequence
#2
Score
58 → 58 (0)
Cluster
mainnet-beta
Slot
425207316
Off-chain at
2026-06-08T23:09:23.211Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
GMKsyhzHJw3ZAmexrgj2hG9XCgz2UPon4EtYkbp5oT32
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1171 chars)
{"actor":"reviewer","decided_at":"2026-06-08T23:09:22.998Z","decision":"review","investigation_id":"a19f2993-f03b-4b55-ba33-7f77dadac14c","new_score":58,"page_slug":"sky-makerdao","prev_score":58,"reason":"The investigation page is broadly accurate and well-sourced, with no outright false claims and no link rot (two URLs redirect but content remains accessible; two return 403 paywalls but content is independently verifiable). The main accuracy issues are: the $6.65M bad debt figure for Black Thursday is contested across sources; the USDS freeze function claim overstates what was actually deployed at launch; the DSChief vulnerability date in the timeline is off by ~3 weeks; and the MKR penalty timeline conflates the May 2025 framework introduction (0% penalty) with the September 2025 penalty activation. The governance centralization section and Black Thursday/legal sections are the strongest parts of the page. Key coverage gaps are on-chain analytics, current financial health, and post-page governance developments.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}