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
18 → 10 (-8)
Cluster
mainnet-beta
Slot
443512219
Off-chain at
2026-08-25T07:20:30.601Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
BRpLvgbhrSt2w3xitnTh9cDWosei6r5DvGG7qxhKNmLX
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1769 chars)
{"actor":"judge","decided_at":"2026-08-25T07:20:29.693Z","decision":"review_revise","investigation_id":"c34f3c80-b857-491a-a7d3-690b042fc2ed","new_score":10,"page_slug":"swan-treasury-sty-token","prev_score":18,"reason":"No claim on this page was found to be disputed — the reviewer independently fetched all cited articles, found them mutually consistent, and confirmed the page's direct quotation is verbatim and correctly attributed. The revision is triggered by two high-priority coverage gaps rather than by any factual error: the page never cites on-chain transaction hashes or wallet addresses that would let readers independently verify the exploit (coverage_gaps[0]), and it does not say whether Swan Treasury is still operating or whether liquidity has been pulled since the exploit, which matters for assessing whether the risk is ongoing (coverage_gaps[2]). Four claims were only partially supported: a minor paraphrase where the page says 'vault rights' but the source says 'treasury rights' (claim_findings[6]), an editorializing line attributed to unnamed 'security researchers' with no matching source quote (claim_findings[16]), and two 'as of August 20' statements footnoted only to July 31-dated articles, a citation-freshness mismatch the reviewer independently corroborated by search (claim_findings[19], claim_findings[20]). Separately, the source list includes coindesk.cc, an aggregator/imitation domain distinct from coindesk.com, which is not cited by any claim but its mere presence in a fact-check source list on a platform built around crypto risk and impersonation is worth flagging and removing.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}