Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#7
Score
51 → 51 (0)
Cluster
mainnet-beta
Slot
462182905
Off-chain at
2026-10-27T19:06:32.701Z
Anchored at
2026-10-27T19:06:42.000Z
Block time
2026-10-27T19:06:42.000Z

Independent verification

1. Database (off-chain)
8kDdj9k4i4jPs5FBVgGADB9cnHTPbmL1uHHJGTPmg3qd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2091 chars)
{"actor":"judge","artifact_identity":"e0745088b4a080a94e0ae40220a25cc7","band_override":null,"decided_at":"2026-10-27T19:06:32.398Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"81428e11-1d41-4a04-9369-d9826a55dfe9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"btcpay-server-lnd-macaroon-credential-exploit-august-2026","prev_score":51,"reason":"The core account holds up: the August 7 advisory, the v2.4.2 patch, the Foundation and Citadel21 thefts, and the bounty terms are supported by the official advisory, release notes, CoinDesk and The Block (claim_findings[0], [1], [6]). Four claims are only partly supported. The page says on-chain hot wallets are at risk and tells operators to move funds, but the current official advisory says they are not affected (claim_findings[3]). The macaroons.db deletion procedure is not in the official advisory (claim_findings[4]), and the Red Team member list was not confirmed (claim_findings[5]). Two archive links point to unrelated articles (claim_findings[7], [8]). The page also does not reflect the October 14 advisory update or whether the promised postmortem has appeared (omission_findings[0]; high-priority coverage gap), so a minor penalty is applied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"score_limit":{"applied":0,"limited":true,"proposed":-10,"rule":"limited_no_second_opinion","second":null},"sequence_num":7,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Claim findings alone give 0% disputed/unverifiable (0 of 9), but omission_findings[0] is material: the official advisory was updated Oct 14, 2026 and now says on-chain hot wallets are not affected, which the page still presents as at risk with a hot-wallet migration step. The page also does not reflect post-August status. Escalating to the minor band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}