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.

Decision
review_approve_with_notes · Sweat Economy (SWEAT Protocol)
View on Solana ↗
Sequence
#3
Score
42 → 58 (+16)
Cluster
mainnet-beta
Slot
443508917
Off-chain at
2026-08-18T21:01:34.680Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
2mwAo5x7XoUEKx7Z5jQqdP7uT3cUQbvqTeEvqumbF94U
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2559 chars)
{"actor":"judge","decided_at":"2026-08-18T21:01:34.494Z","decision":"review_approve_with_notes","investigation_id":"92e0c575-a6d1-42dd-81e7-240757082fb7","new_score":58,"page_slug":"sweat-economy-sweat-protocol","prev_score":42,"reason":"Content accuracy holds up: 11 of 18 claims confirmed, and the two disputed findings (claim_findings[9] on vulnerability-disclosure status, claim_findings[11] on the ATH price/date) are secondary figures and a stale characterization, not errors that change the reader's conclusion about the incident itself. The score question is separate and is where the real correction lies: the page's only substantive incident is a smart-contract exploit the entity suffered from an external, unidentified attacker (calibration_assessment.incident_attributions[0]-[1], both attribution 'b'), with an unusually strong response — contract paused on detection, a coordinated MEXC/Rhea Finance freeze, and 100% restoration of external balances within about a week. Per the rubric's own anti-conflation guidance, a suffered incident with no entity-side fraud or negligence caps in CAUTIONARY (50-69), not WARNING (20-49); the current 42/WARNING score is scoring the exploit's scale as if it were own-conduct, which the evidence does not support. Residual risk factors (no official Sweat Foundation post-mortem, undisclosed post-patch audit status, unaddressed supply-concentration structure) justify keeping the score in the middle of CAUTIONARY rather than pushing it into VERIFIED territory, consistent with the reviewer's recommended 58. Notes: (Correct the ATH figure: CoinGecko and CoinMarketCap independently agree on ~$0.091-0.093 at the Sept 2022 TGE, not $0.0181/March 2024 from CoinLore; the >99% decline conclusion is unaffected either way.) (Update the vulnerability-disclosure claim: Fireblocks published a specific root-cause technical writeup (missing #[private] macro on ft_resolve_transfer) in June 2026, predating this page's own source-archiving dates. Reframe as 'Sweat Foundation has not published an official post-mortem, though independent security firm Fireblocks published a technical root-cause analysis in June 2026.') (Correct the May 2026 low-price timeline date from May 1 to May 8 per CoinGecko.) (Add coverage of whether the patched contract has undergone an independent post-incident audit, and of SWEAT's regulatory status, as the reviewer's coverage gaps flag.)","score_delta":16,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}