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_revise · Quant Network
- Sequence
- #3
- Score
- 68 → 58 (-10)
- Cluster
- mainnet-beta
- Slot
- 424157067
- Off-chain at
- 2026-06-04T02:54:23.732Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4n6EP5SPFLb7H1p4Mnm8uxL4cKKACHpQzcae3KNZduQv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1311 chars)
{"actor":"judge","decided_at":"2026-06-04T02:54:23.521Z","decision":"review_revise","investigation_id":"1a8ab90d-615d-437f-911e-9003da98fe20","new_score":58,"page_slug":"quant-network","prev_score":68,"reason":"The review found no outright disputed claims but identified three unverifiable assertions and four partially supported claims across 21 total findings, yielding a disputed percentage of approximately 14%. The most significant weaknesses are: the FINMA utility token classification in the regulatory section (claim_findings[12]) has no cited or findable source; the ICO fundraising figure (claim_findings[14]) conflates the public sale total with aggregate multi-round fundraising, understating total raised by roughly $15M; and the reserve token count (claim_findings[17]) is imprecise at approximately 2.6M versus the stated 2M. Two cited sources (fintechmagazine.com, ukfinance.org.uk primary) returned HTTP errors, though both underlying claims are confirmed through alternative sources. Two high-priority coverage gaps — on-chain QNT token holder concentration and a direct FCA register check — should be addressed to strengthen the regulatory section.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}