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.

Sequence
#3
Score
7868 (-10)
Cluster
mainnet-beta
Slot
443523833
Off-chain at
2026-08-27T05:08:45.293Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
7iv5BRvSCMQgQoDfMrPnZavC6vLbcRRJnsk3RFFM1LtK
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1735 chars)
{"actor":"judge","decided_at":"2026-08-27T05:08:45.046Z","decision":"review_revise","investigation_id":"271e2e99-0e03-4268-a81d-53f986183221","new_score":68,"page_slug":"spiko-eu-t-bills-money-market-fund","prev_score":78,"reason":"Of 40 claims checked, 6 were disputed, giving a disputed rate of 15% (6/40) — within the minor-issues band. Three of those disputes (claim_findings[33], [35], [36]) are timeline dates where the cited source gives a specific day that differs from the page's date; that is treated as a genuine contradiction rather than the rounding seen elsewhere on the page, where sources only offered a month and the finding was correctly marked partially supported instead. A fourth (claim_findings[34]) is more serious: the page's timeline says Spiko obtained MiFID status a full year before the date the page's own body text gives for the same event (claim_findings[11]), an internal contradiction rather than a sourcing gap. The page also states one TVL figure from the same source three different ways in different places (claim_findings[20]) and misdescribes a cited ECB bulletin as not naming Spiko when the reviewer found it does (claim_findings[29]) — both accuracy problems with how the page handles its own citations. Weighed against this, the page's core substantive claims — the fund's regulatory classification, manager, custodian, and technical architecture — were independently verified against primary sources with no factual errors and no adverse allegations were found anywhere on the page, which keeps the penalty toward the lower end of the revise band.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}