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 · ArbiSwap
- Sequence
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464291240
- Off-chain at
- 2026-11-02T00:19:08.876Z
- Anchored at
- 2026-11-02T00:19:39.000Z
- Block time
- 2026-11-02T00:19:39.000Z
Independent verification
- 1. Database (off-chain)
- E42LTaxPVeoyAyekqDrEMpTYFFv8FAr8dQ6PZJD29P8U
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1595 chars)
{"actor":"judge","artifact_identity":"7fab8ecaa4851876589084b4a08e31f4","band_override":null,"blocked_count":2,"decided_at":"2026-11-02T00:19:08.625Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"abc33bc1-50c8-4c5b-b465-b896e5299045","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"arbiswap","prev_score":0,"reason":"The core account holds up: the February 24, 2023 launch, the March 2, 2023 rug pull, the 68.47 ETH mint-dump and the Tornado Cash routing are supported by CryptoSlate and CoinDesk (claim_findings[0], [1], [3]). Of the 6 claims that could be checked, 1 was unverifiable (the ZachXBT flag, claim_findings[7], where the page's own text admits no specific report was found), about 17%. The separate arbitrage bot that supposedly made $112,000 (claim_findings[2]) appears to double count the deployer's own proceeds, which affects the rug-pull mechanics section. Two claims about the contract swap 13 hours before the rug (claim_findings[4], [5]) could not be checked because the cited source blocked the reviewer; they are left out of the percentage and are a coverage limit, not a defect. The page needs correction on the bot figure and the ZachXBT section, and it should note that the sources give different loss figures.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}