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 · NEAR Protocol
- Sequence
- #3
- Score
- 72 → 64 (-8)
- Cluster
- mainnet-beta
- Slot
- 424135194
- Off-chain at
- 2026-06-04T00:28:32.427Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GYFTFkSSvKGru87pZyrBDT7oxvRjWzVMK18G46EtkyCo
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1466 chars)
{"actor":"judge","decided_at":"2026-06-04T00:28:32.219Z","decision":"review_revise","investigation_id":"5dfc3991-d810-433a-868c-cc8880f85b96","new_score":64,"page_slug":"near-protocol","prev_score":72,"reason":"The page is substantively accurate on all core claims — founding history, funding rounds, security incidents, and regulatory filings are confirmed by Tier 1 sources with no claims outright disputed. However, the reviewer identified two factual inaccuracies warranting correction: claim_findings[6] states the shard count before Nightshade 2.0 was four, but sources indicate it was six at the time of that upgrade; and claim_findings[25] describes the May 2026 FIPS-204 announcement as mainnet integration when sources confirm only a testnet deployment was planned, with mainnet to follow security audits. Five additional claims are unverifiable due to dynamic on-chain data (validator count, genesis allocation percentages, geographic Nakamoto coefficient, token holder concentration, marketing-stunt price drop) — none are contradicted by sources. A medium-priority coverage gap notes the governance controversy surrounding the October 2025 inflation halving, where a failed community vote was overridden by the development team via protocol upgrade; this omission understates a material centralization concern.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}