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 · GHO
View on Solana ↗
Sequence
#3
Score
6153 (-8)
Cluster
mainnet-beta
Slot
443524676
Off-chain at
2026-08-27T07:09:26.523Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
7rv64mp3GQGSjmuR8KCqii8JVKQDv5NXLi4gP1LxV8p
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2200 chars)
{"actor":"judge","decided_at":"2026-08-27T07:09:26.340Z","decision":"review_revise","investigation_id":"fdad1101-684b-4137-b3ab-e68d28005c64","new_score":53,"page_slug":"gho","prev_score":61,"reason":"Of 44 claims checked, only claim_findings[39] and claim_findings[42] are disputed and claim_findings[43] is unverifiable, giving a disputed_pct of 6.8% — well within the approve band, and the two disputed items are exact-day discrepancies of a few days on dates the surrounding prose already states more loosely (a repeg pinned to Feb 6 vs. the page's Feb 1, and an sGHO launch pinned to April 3 vs. the page's April 1), not disputes over the page's core claims. The reviewer also confirms the page gets the hard parts right: it classifies GHO's mechanism correctly throughout and reports the 2023-24 depeg accurately as both real and resolved. What moves this out of a clean approval are two high-priority coverage gaps and a concentrated staleness problem that the disputed_pct figure does not capture. Four stale findings (claim_findings[22-25]) show an entire 'Collateral Concentration' section, plus part of the GSM discussion, resting on a single LlamaRisk report from June 2024 — over two years old relative to the page's mid-2026 framing — presented with no as-of date, on exactly the topic (collateral risk) a reader would expect to be current. Separately, the review flags two high-priority coverage gaps: a complete absence of any mention of GHO's real, findable smart-contract audits (OpenZeppelin, SigmaPrime, ABDK, Certora), and no discussion of the GHO Stewards multisig that exercises the very governance discretion the page itself flags as a risk. Neither gap is a fabrication or an adversarial omission — the audit silence is arguably favorable-to-subject in effect since it withholds a credibility-boosting fact rather than distorting a risk one — but the combination of two high-priority gaps and a stale, undated core risk section is enough to warrant revision rather than a bare approval, per the reviewer's own coverage-gap guidance.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}