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 · MemeCore
View on Solana ↗
Sequence
#3
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
464266713
Off-chain at
2026-11-01T22:51:54.553Z
Anchored at
2026-11-01T22:52:15.000Z
Block time
2026-11-01T22:52:15.000Z

Independent verification

1. Database (off-chain)
BEbYVz4jsvo8iM5zK1E3GDuPmrFcfhsH1LeUAiTqk2bj
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1531 chars)
{"actor":"reviewer","artifact_identity":"ff780eb0b32ea69a3f1411032d71890d","blocked_count":2,"decided_at":"2026-11-01T22:51:54.477Z","decision":"review","disputed_pct":0.125,"findings_hash":"44WaxwPcTxbQ56K7p8SFPEzJbd5KReFBu6YwgRP1G2dm","investigation_id":"2038f16c-26d5-4841-afcf-f8018e776e64","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"omissions":{"material":0,"total":1},"page_content_hash":"bee1ad69809bfa913b472dc3ead4ea0a3530a6f6442aa9ddbbc69ddd6596661c","page_slug":"memecore","prev_score":26,"reason":"The core narrative is supported: the June 2026 crash, the team silence, the listing details, the September 2025 Block press release and the CertiK audit counts all match their sources. Problems found are a CertiK major-holding figure that no longer matches the live page (97.30% versus 87.4%), an unsourced mainnet day (February 12, 2025), and a slightly stronger wording than CoinDesk's 'did not immediately respond'. Several claims could not be checked because CryptoTimes and CCN were blocked. Only about ten of the page's many claims were checked, and the page does not state any shutdown, sanction or regulatory action that I could contradict.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}