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.

Decision
review · SwissBorg
View on Solana ↗
Sequence
#2
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
425424104
Off-chain at
2026-06-09T23:06:01.866Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
2ErDdMhp9uRParPPrhKncgqWbib5igRfboKFfjahp1cw
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (993 chars)
{"actor":"reviewer","decided_at":"2026-06-09T23:06:01.736Z","decision":"review","investigation_id":"524894ae-ff61-4c27-9e9e-0f8c8069ce3e","new_score":52,"page_slug":"swissborg","prev_score":52,"reason":"The core factual claims about the September 2025 Kiln/SwissBorg exploit are well-supported by multiple independent credible sources, including Kiln's own post-mortem, The Record, Protos, and on-chain analysis. The two most notable errors are: (1) the Proof of Liabilities launch date is listed as June 2024 when it was actually launched in April/May 2023 — a 13-month discrepancy likely caused by confusing an audit snapshot ID with the launch date; and (2) the MiCA authorization date is listed as March 11 when the AMF registry shows March 5. All cited URLs that were tested are live and support their associated claims. No link rot was detected.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}