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
#3
Score
7255 (-17)
Cluster
mainnet-beta
Slot
443524023
Off-chain at
2026-08-27T05:39:04.204Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
229xHhLNwaEwayD2zdKuG2QZHkCaZy8JEgmMK7aesoo3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2338 chars)
{"actor":"judge","decided_at":"2026-08-27T05:39:04.039Z","decision":"review_revise","investigation_id":"bb517309-c0a3-4700-aa9e-b7d4a3c9ce6d","new_score":55,"page_slug":"janus-henderson-anemoy-aaa-clo-fund-jaaa","prev_score":72,"reason":"An independent fact-check of this page's 26 sourced claims found 16 fully confirmed, 2 with only a minor citation mismatch, but 5 disputed and 3 unverifiable -- 8 of 26 (31%), just over this project's threshold for a 'significant issues' escalation. Four of the five disputed items are date errors in which the page's own cited article names a different day than the page states: a Particula rating dated Nov 1, 2025 versus the report's own Nov 4-5 date (claim_findings[24]), a Kraken Custody announcement dated June 29 versus the cited article's own June 25, 2026 (claim_findings[8] and [27]), and an Ethena partnership entry dated June 12 versus its cited source's June 9, 2026 (claim_findings[26]). The fifth, and most substantive, disputed item is that the page describes a Wintermute liquidity partnership as covering this fund (JAAA), when the announcement it cites says the arrangement initially covers a sibling fund (JTRSY) only -- the review found JAAA's real liquidity mechanism is a separate, later partnership the page never mentions (claim_findings[19]). Weighing the other side: the review's highest-priority check -- confirming the page does not wrongly import a sibling fund's management structure -- passed cleanly against the fund's own rating report, with no party mislabeled (claim_findings[1]); the page's sole adverse item, a 2019 regulatory fine against a corporate predecessor, is precisely sourced and fairly caveated as unrelated to the current fund (claim_findings[18]); there is no link rot or staleness anywhere in the citation set; and no coverage gap was rated high-priority. On balance the page's core institutional facts hold up well, but the cluster of self-contradicting dates plus one unsupported and materially relevant liquidity claim is enough real inaccuracy to warrant revision and a closer look, not approval outright, though not the higher-penalty band reserved for pages with a majority of disputed core claims.","score_delta":-17,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}