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.

Decision
review · MANTRA Chain
View on Solana ↗
Sequence
#2
Score
22 → 22 (0)
Cluster
mainnet-beta
Slot
443523147
Off-chain at
2026-08-27T03:22:42.968Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
5dQNLkGbuiY8ZxTCWEEHTKuGRr6ZeBgfg2EMxE52sSBq
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1401 chars)
{"actor":"reviewer","decided_at":"2026-08-27T03:22:42.847Z","decision":"review","investigation_id":"0ffbfa7c-6f53-4b54-9379-116f5a65d8f5","new_score":22,"page_slug":"mantra-chain","prev_score":22,"reason":"The page's core narrative of the August 2026 Cosmos EVM exploit and chain halt is well-sourced and independently corroborated in almost every particular, including cross-chain details about KiiChain and TAC. The weakest parts of the page are its treatment of the April 2025 OM collapse: it overstates Glassnode's actual (narrower) finding into a de facto exoneration of the team on a causal question that remained genuinely and publicly contested at the time, it misstates the token burn figures by roughly half (apparently conflating dollar value with token count), and one timeline date (mainnet launch) defaults to the first of the month in a way that is verifiably wrong by three weeks. The page also omits several highly relevant, independently verifiable facts — the March 2026 OM-to-MANTRA 1:4 token rebrand, the 2024 supply increase and insider-concentration allegations, the specific VARA Dubai license, and a settled Hong Kong governance dispute involving the CEO — that materially affect a full tokenomics and trust assessment of this entity.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}