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 · Wise Lending V2
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464344827
- Off-chain at
- 2026-11-02T03:30:55.165Z
- Anchored at
- 2026-11-02T03:31:05.000Z
- Block time
- 2026-11-02T03:31:05.000Z
Independent verification
- 1. Database (off-chain)
- BTzMvpanoAUdGQQqx7i1FTwvE91NTZW1LzcrzuFCf4fA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1717 chars)
{"actor":"judge","artifact_identity":"8267f8c33777625249a201add5764715","band_override":null,"decided_at":"2026-11-02T03:30:54.892Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"7bbe4d9d-74e7-4ff7-b64b-d7a630072930","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"wise-lending-v2","prev_score":52,"reason":"Of 10 checked claims, 5 (50%) could not be verified, which places the page in the significant-issues band. The core allegation of an October 2023 exploit, the 'second attack within six months' quote, the $720,000+ total (claim_findings[0], [1], [5]) and the ZachXBT attribution (claim_findings[6]) were not found in any cited or searched source. The claim that the protocol 'continues to operate' is stale because DeFiLlama lists it as deprecated (claim_findings[8], subject_status). The January 2024 exploit and the Code4rena audit facts were confirmed, so the page is revised rather than denied. The reviewer's confidence is moderate (0.6), and DeFiLlama could not be fetched directly.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission and says the page contradicts the subject's current status: DeFiLlama labels the protocol deprecated with zero active loans, while the page says it continues to operate. This supports at least the significant band, which matches the percentage band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}