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 · Web3Port
- Sequence
- #2
- Score
- 5 → 5 (0)
- Cluster
- mainnet-beta
- Slot
- 443561568
- Off-chain at
- 2026-09-02T00:38:48.047Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5isb9b9SJi8iiAibLfZfsUL94MD4afeawS5ExT4UVSse
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1242 chars)
{"actor":"reviewer","artifact_identity":"03c657dad9ed7233774e42eae699e58d","decided_at":"2026-09-02T00:38:47.924Z","decision":"review","disputed_pct":0,"investigation_id":"987d9530-9591-480a-943c-b6d7da493ab1","new_score":5,"page_slug":"web3port","prev_score":5,"reason":"The page's factual claims are unusually well-corroborated against independent reporting: dates, dollar figures, court records (Delaware Chancery advancement ruling), and the NYT/Aqua1/Zhou reporting chain all check out closely against primary and secondary sources located independently. The page consistently and accurately distinguishes confirmed facts from third-party allegations (e.g., Web3Port's identity as the banned market maker, the GPS/SHELL attribution) that remain unconfirmed by Binance or any regulator. The only substantive issues found were a minor creditor-name error in the bankruptcy section (Division of Corporations vs. Division of Revenue) and one summary-level sentence that slightly overstates Binance's confirmation of Web3Port's identity relative to the more careful hedging used in the body sections.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}