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 · SIGMA Bot
View on Solana ↗
Sequence
#6
Score
4 → 4 (0)
Cluster
mainnet-beta
Slot
423953605
Off-chain at
2026-06-03T04:23:52.859Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
5cqsq8jj3LAE6deCKKRVLoLDyw5Qz9ThktLKaosZJ3jH
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1022 chars)
{"actor":"reviewer","decided_at":"2026-06-03T04:23:52.659Z","decision":"review","investigation_id":"cfa54088-9549-4a76-a3e8-6567fa5722af","new_score":4,"page_slug":"sigma-bot","prev_score":4,"reason":"The investigation is factually solid on its core claims. The May 11, 2026 incident details, wallet origin analysis, @k0braca1 analyst findings, comparative Telegram bot incidents, and SIGMA's silence are all independently confirmed. Two source URLs are inaccessible (CoinTelegraph 404, Defiant 403) and one ForkLog quote lacks a traceable citation, but the underlying facts in all three cases are verified through alternative sources. The most significant structural gap is the absence of direct on-chain trace evidence and documented inspection of SIGMA's own post-incident communication channels, which would further substantiate the central attribution and no-response claims.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}