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.

Sequence
#4
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
454774817
Off-chain at
2026-10-09T05:39:52.522Z
Anchored at
2026-10-09T05:39:55.901Z
Block time
—

Independent verification

1. Database (off-chain)
6UMWTLWUvgRTaTCASWWcaLPZLeHTzvvTvcBrChnH8BwD
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2028 chars)
{"actor":"reviewer","artifact_identity":"2d3fb7658463ccb154327f2a20e159f2","decided_at":"2026-10-09T05:39:52.142Z","decision":"review","disputed_pct":0.1515,"findings_hash":"9Darum9r5ESV7unBnHb3EhHAL4qP611FJU9yEoLEdZKH","investigation_id":"1056b75f-82b1-488c-ad72-1d1b7e5ad675","mode":"findings_only","new_score":28,"page_content_hash":"d57429b71029b302f7a2054c27328eb481d40f63e8b00fc67c436685ef04d656","page_slug":"origin-protocol","prev_score":28,"reason":"The page's core narrative — the November 17, 2020 OUSD reentrancy/flash-loan exploit, the pre-launch audit gap, the compensation plan terms and claim-window dates, the post-exploit audit sequence (Trail of Bits, Solidified, OpenZeppelin), the funding history, the OGN all-time high, team backgrounds, and the absence of SEC/CFTC action — holds up well against independent sourcing, including direct verification of the Josh Fraser quote and exact dollar/ETH/DAI figures against primary news coverage. The main defects found are structural rather than factual: two dead citation URLs (blog.peckshield.com, which has no archive fallback, and originprotocol.com/team, which does have one and should simply be swapped to its existing Wayback snapshot), one dead low-tier source (canvasbusinessmodel.com), one timeline date (Super OETH's 'July 2024' launch) that is not supported by any source and conflicts with Origin's own August/September 2024 updates, and current OGN price/market-cap figures that are directionally correct (~98% off all-time high) but not pinned down precisely given wide disagreement across live price trackers. The most substantive gap is the August 2025 'Origin Vault x Levva' claim, which appears in both the timeline and a section but has no citation anywhere on the page and could not be corroborated by any independent source — this warrants sourcing or removal rather than a simple factual correction.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}