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
- #9
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 464252471
- Off-chain at
- 2026-11-01T22:01:13.267Z
- Anchored at
- 2026-11-01T22:01:18.000Z
- Block time
- 2026-11-01T22:01:18.000Z
Independent verification
- 1. Database (off-chain)
- 3MdJmGqX8FupBCGjBUsaWQsZZGfD9aDD6sDisyF2it6P
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1560 chars)
{"actor":"judge","artifact_identity":"fadfdc4307f26d9f6cb22ba953cb0d8a","band_override":null,"decided_at":"2026-11-01T22:01:13.033Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"5dfc3991-d810-433a-868c-cc8880f85b96","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":62,"page_slug":"near-protocol","prev_score":62,"reason":"Of 8 claims checked, 4 were confirmed (claim_findings[0-3]: SEC dismissal, NEAR Intents exploit details, ZachXBT tracing, full return of funds), 1 was only partly supported, and 3 could not be verified (37.5% by the standard count), which falls in the significant-issues band. The unverified items are the MEV bot detail (claim_findings[5]), an uncited sentence about AI-agent branding (claim_findings[6]) and the Nightshade 2.0 date (claim_findings[7]), which are peripheral rather than core allegations, and claim_findings[4] has an ambiguous Aurora bounty figure (the cited source says $1M each, $2M total). Because the reviewer's confidence is moderate (0.6), several items were not fetched, and no core claim was disputed, the penalty sits at the mild end of the band. The omitted Skyward Finance exploit is minor and the subject is operating with the exploit already covered, so no severity override applies.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":9,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}