Skip to main content
AVOID.NET
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 · KAT katana-network
View on Solana ↗
Sequence
#2
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
443525189
Off-chain at
2026-08-27T10:26:43.774Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
AFRrkQ74bdnpnRn72GFSdmd39CFNT4GfmDcj125fP3U9
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1105 chars)
{"actor":"reviewer","decided_at":"2026-08-27T10:26:43.420Z","decision":"review","investigation_id":"c5646ee6-7870-4351-889b-edd75d2b32dd","new_score":52,"page_slug":"kat-katana-network","prev_score":52,"reason":"The page's core narrative (Katana Network's incubation, tokenomics structure, TGE delay, exchange listings, and Stage 0 L2Beat classification) is well-supported by tier-1 and tier-2 sources. However, the page contains a clear internal misstatement of its own cited MEXC source's market-cap and volume-to-market-cap figures (6:1 vs. the source's ~4:1), an unreconciled arithmetic inconsistency between stated price, circulating supply, and market cap for two separate June 2026 snapshots, a first-of-month placeholder timeline date that contradicts the page's own prose, and a probable duplicate/conflicting Upbit listing date in the timeline. Several granular L2Beat technical risk claims could not be independently verified due to access limitations.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}