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 · Revolut Data Breach (Fake Government Request, September 2026)
- Sequence
- #3
- Score
- 30 → 5 (-25)
- Cluster
- mainnet-beta
- Slot
- 464352406
- Off-chain at
- 2026-11-02T03:57:44.575Z
- Anchored at
- 2026-11-02T03:58:12.000Z
- Block time
- 2026-11-02T03:58:12.000Z
Independent verification
- 1. Database (off-chain)
- 6zqUKqp282n2n13JtzdN4RPdYCK5nNuWe1gwuEspAFDv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2627 chars)
{"actor":"judge","artifact_identity":"9d0c038e5d87d3a8addbbef85cb3cb2c","band_override":{"actual_delta":-28,"actual_verdict":"review_revise","disputed_pct":0.625,"expected_delta_range":[-50,-30],"expected_verdict":"review_deny","rationale":"Five of eight checked claims (62.5%) were disputed or could not be verified, which on numbers alone falls in the failing band. Two disputed findings (claim_findings[0] and [1]) show the page attributes the figure of about 680 affected customers to Revolut, when Revolut only said a 'limited' number and the figure came from the hackers and press reports. Three further claims (Reggio Calabria, ZachXBT, the Sept 11 notification date) were not found in the sources cited for them (claim_findings[2], [3], [4]). The verdict is held at revise rather than deny because the reviewer's confidence is low (0.5), only three of the cited sources were read, the three unverified items are source-matching gaps rather than contradictions, and the core account (the breach, the ransom demand, the credential findings) was confirmed (claim_findings[6])."},"decided_at":"2026-11-02T03:57:44.356Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.625,"investigation_id":"90b40c3c-e5f4-4306-b5dc-a1d036dbe1f0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":5,"page_slug":"revolut-data-breach-fake-government-request-september-2026","prev_score":30,"reason":"Five of eight checked claims (62.5%) were disputed or could not be verified, which on numbers alone falls in the failing band. Two disputed findings (claim_findings[0] and [1]) show the page attributes the figure of about 680 affected customers to Revolut, when Revolut only said a 'limited' number and the figure came from the hackers and press reports. Three further claims (Reggio Calabria, ZachXBT, the Sept 11 notification date) were not found in the sources cited for them (claim_findings[2], [3], [4]). The verdict is held at revise rather than deny because the reviewer's confidence is low (0.5), only three of the cited sources were read, the three unverified items are source-matching gaps rather than contradictions, and the core account (the breach, the ransom demand, the credential findings) was confirmed (claim_findings[6]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-25,"score_limit":{"applied":-25,"limited":true,"proposed":-28,"rule":"second_opinion_agreed","second":-25},"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}