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
- 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. - 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.
- 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 · Port3 Network
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464346353
- Off-chain at
- 2026-11-02T03:36:07.890Z
- Anchored at
- 2026-11-02T03:36:35.000Z
- Block time
- 2026-11-02T03:36:35.000Z
Independent verification
- 1. Database (off-chain)
- HCh3h6NmRQeZzEG27Kv3XDtPWLyMjo3VveQ7DvptbBb7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1430 chars)
{"actor":"reviewer","artifact_identity":"621868989c910c3ba462c6869635c49b","decided_at":"2026-11-02T03:36:07.841Z","decision":"review","disputed_pct":0.6,"findings_hash":"6WiNKK1qS33ka1ARMBJLicAjVTS6rL61EbeNU8TpUxxL","investigation_id":"1b3b0823-c7ff-46a7-ac65-5870db5a63d3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_content_hash":"e68a926958f51701f20ca59e24176698b97cee8588754240d663193356bdc12e","page_slug":"port3-network","prev_score":58,"reason":"The core exploit narrative (CATERC20 flaw, 1B tokens minted, about 162M sold for about $166K, 80% drop, 1:1 BNB Chain migration with a 162.7M burn) is corroborated. Errors found: the Kraken December 2025 delisting claim is contradicted by Kraken's own notice, the attacker registration date (Nov 23) conflicts with Nov 22 elsewhere, and the Dec 24 Coinone timeline entry has no support. The ZachXBT flag is stated as fact in the summary but is unsourced and admitted unverified in the body. The cited onesafe URL no longer carries the Coinone article. Many funding, tokenomics and market-data claims were not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}