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
4 → 0 (-25)
Cluster
mainnet-beta
Slot
443522999
Off-chain at
2026-08-27T03:14:12.622Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
2qSjusnpn7tgDzxT2wZUdr1DTnZmfStGXY4APsNmKvGo
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1670 chars)
{"actor":"judge","decided_at":"2026-08-27T03:14:12.341Z","decision":"review_revise","investigation_id":"bb0f5270-464b-4b29-bfc6-0040fd189172","new_score":0,"page_slug":"step-finance-ai-agent-over-permission-exploit-january-2026","prev_score":4,"reason":"The page's factual backbone — the theft amount, the executive-device compromise, the shutdown, the Harrap quotes, the laundering route, and the recovery figure — checks out against independent tier-1/2 reporting (12 of 23 claims confirmed). However, the claim that gives this investigation its name and framing — that autonomous AI trading agents with unconstrained transfer authority amplified the breach — is disputed: no primary or forensic source corroborates it, and one of the page's own three cited sources for that claim contradicts it when read directly (claim_findings[10]). Compounding this, the page's own attack-vector section states the breach was 'entirely operational... relying on stolen signing credentials' (claim_findings[9]), which is itself confirmed by independent sources but directly conflicts with the AI-agent section elsewhere on the same page — an internal self-contradiction, not merely an unsupported assertion. A secondary, lower-stakes error was also found in the STEP token's all-time-high date. Given disputed_pct of 0.39 falls in the 30-60% band, and the disputed material concerns the page's central thesis rather than a peripheral detail, this warrants substantial revision and a public flag while the sound factual core is preserved.","score_delta":-25,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}