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 · Rahul Ravinder Malhotra
- Sequence
- #3
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 462360255
- Off-chain at
- 2026-10-28T05:35:56.093Z
- Anchored at
- 2026-10-28T05:36:24.000Z
- Block time
- 2026-10-28T05:36:24.000Z
Independent verification
- 1. Database (off-chain)
- CNYh4tc523xrP1iawpoiZBmEYPpSNupUurqavGus1PHK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1774 chars)
{"actor":"reviewer","artifact_identity":"dfc6e3121a0608a3c41b6474b1b986e3","blocked_count":2,"decided_at":"2026-10-28T05:35:55.906Z","decision":"review","disputed_pct":0,"findings_hash":"2MTEuV8EMxwZWvLDZS3zS9CBCXcgppJjEgT9SFDaSrV4","investigation_id":"c9aeffa8-3c0e-48d1-93f8-1cef120ab8fe","mode":"findings_only","new_score":35,"page_content_hash":"9065efdbfe16d9ce2fd6a526d2c339c6012903396c58cb85254c00469a196d97","page_slug":"rahul-ravinder-malhotra","prev_score":35,"reason":"This is a clearance-style page concluding there is no credible evidence tying any 'Rahul Ravinder Malhotra' to crypto risk, and independent re-checking supports that conclusion: broad searches for the name plus crypto, fraud, SEC/CFTC/DOJ/OFAC/SEBI terms all come back empty, and the one specific factual claim on the page — the June 2024 Prabhudas Lilladher CBDO appointment — is corroborated by the cited HR Today article (a low-tier but on-point source). The main defect is evidentiary thinness on the name-collision side: the LinkedIn 'dozens of distinct profiles' claim could not be independently verified because LinkedIn blocks automated access, and the cited Radaris URL has gone dead (the domain was seized under a New Jersey court judgment and no longer hosts any public-records content), though the page's own source metadata had already marked it unarchivable. No material omissions were identified since the page is transparent about the limits of what it could find.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}