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 · Base
View on Solana ↗
Sequence
#3
Score
78 → 68 (-10)
Cluster
mainnet-beta
Slot
423946102
Off-chain at
2026-06-03T03:33:59.402Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
4ZRHPwhqu9m2aMecaaecE2mHaq2ct1Qu7wNFywJo7SWY
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1610 chars)
{"actor":"judge","decided_at":"2026-06-03T03:33:59.262Z","decision":"review_revise","investigation_id":"eb1f07c6-750b-4b1b-afe7-4d6de6d21833","new_score":68,"page_slug":"base","prev_score":78,"reason":"The reviewer found 1 disputed claim out of 24 (12.5%), placing this in the minor-revision band. The disputed claim (claim_findings[1]) is the page's $4.6B TVL figure paired with the 'largest L2 by DeFi TVL' characterization: reviewer evidence shows Base's total TVL was approximately $11–13B as of May 2026, making the figure significantly stale and conflating DeFi TVL share (~46%) with absolute total TVL. This is flagged as a high-priority coverage gap and affects the page summary. Three additional claims are partially supported: the $30M annual sequencer revenue figure is an outdated 2024 estimate (claim_findings[9]); the 'approximately 7%' OP token decline is not confirmed by any single primary source (claim_findings[22]); and the Azul timeline date of 2026-05-29 should be 2026-05-28 per multiple sources (claim_findings[18]). One cited source returns HTTP 404 (link rot on a Tier 3 dev.to URL), though the underlying facts are independently confirmed by an official post-incident report. The page's core qualitative risk analysis — sequencer centralization, Stage 1 decentralization, Azul upgrade mechanics, regulatory exposure, and incident history — is broadly confirmed by Tier 1 sources and does not require revision beyond the data updates noted.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}