← Zeus Network2 decisions on this page
Audit log
Every state-changing event for Zeus Network: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1reviewby reviewerreviewer2026-07-24 01:02:36ZScore: 42 → 42 (no score change)The page's core factual scaffolding (funding, team, token mint, ATH/drawdown, APOLLO/zBTC timeline) checks out against independent sources, and its central editorial judgment -- that the watchdog tip's most serious claims (deleted Discord, unreachable team) are unverified while the Astarter 'acquisition' is a real but one-sided, uncorroborated announcement -- is accurate and, if anything, conservative. Independent checking in this review found a live, populous Discord invite (confirming, not just failing to refute, that the server is not deleted) and found the page's own cited TVL source (bitcointreasuries.net) shows materially higher current zBTC holdings than the figure the page actually printed, sourced instead from a weaker aggregator. No claim was found to be disputed or contradicted by more credible sources.anchoranchored
- chain
- ●mainnet-betaslot 443,501,720
- sig
2vtRT9xt1H4w…3Q9PzuWbexplorer ↗- hash
DkoFotXQANz5…sp2LxTw2sha256 → base58
verifying row…full verify ↗canonical bytes (1173 B) ▸
{"actor":"reviewer","decided_at":"2026-07-24T01:02:36.116Z","decision":"review","investigation_id":"e426ee73-b31d-4633-80c0-71ffac4c5d68","new_score":42,"page_slug":"zeus-network","prev_score":42,"reason":"The page's core factual scaffolding (funding, team, token mint, ATH/drawdown, APOLLO/zBTC timeline) checks out against independent sources, and its central editorial judgment -- that the watchdog tip's most serious claims (deleted Discord, unreachable team) are unverified while the Astarter 'acquisition' is a real but one-sided, uncorroborated announcement -- is accurate and, if anything, conservative. Independent checking in this review found a live, populous Discord invite (confirming, not just failing to refute, that the server is not deleted) and found the page's own cited TVL source (bitcointreasuries.net) shows materially higher current zBTC holdings than the figure the page actually printed, sourced instead from a weaker aggregator. No claim was found to be disputed or contradicted by more credible sources.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 98c00635-b2f5-4aed-afb8-526fa4773f3e - #2review reviseby judgejudge2026-07-24 01:02:36ZScore: 42 → 37 (-5)The reviewer found no disputed claims out of 17 checked (disputed_pct 0.06), with 12 confirmed, 4 partially supported on minor precision points (claim_findings[6] job-title nuance, [9] rank estimate, [14] a single date, [15] an understated TVL figure), and 1 unverifiable low-priority founding-year detail (claim_findings[16]). The page's central editorial judgment -- that the abandonment allegations are unverified rather than confirmed -- held up and was, if anything, conservative relative to what independent checking found (claim_findings[3], [13]). However, the reviewer flagged two high-priority coverage gaps that go to the heart of the abandonment/exit-risk question this page exists to answer: no analysis of treasury or insider wallet activity, and no review of the Bitcoin custody bridge's security/audit history despite it holding tens of millions of dollars in assets. Because these gaps concern the page's core risk thesis rather than peripheral detail, they merit a modest revision rather than a clean approval, even though no factual claim on the page was disputed.anchoranchored
- chain
- ●mainnet-betaslot 443,501,731
- sig
3dGQCWR6jgk3…86JZi3zCexplorer ↗- hash
7JycBp7FJVfU…f36d7DNAsha256 → base58
verifying row…full verify ↗canonical bytes (1436 B) ▸
{"actor":"judge","decided_at":"2026-07-24T01:02:36.116Z","decision":"review_revise","investigation_id":"e426ee73-b31d-4633-80c0-71ffac4c5d68","new_score":37,"page_slug":"zeus-network","prev_score":42,"reason":"The reviewer found no disputed claims out of 17 checked (disputed_pct 0.06), with 12 confirmed, 4 partially supported on minor precision points (claim_findings[6] job-title nuance, [9] rank estimate, [14] a single date, [15] an understated TVL figure), and 1 unverifiable low-priority founding-year detail (claim_findings[16]). The page's central editorial judgment -- that the abandonment allegations are unverified rather than confirmed -- held up and was, if anything, conservative relative to what independent checking found (claim_findings[3], [13]). However, the reviewer flagged two high-priority coverage gaps that go to the heart of the abandonment/exit-risk question this page exists to answer: no analysis of treasury or insider wallet activity, and no review of the Bitcoin custody bridge's security/audit history despite it holding tens of millions of dollars in assets. Because these gaps concern the page's core risk thesis rather than peripheral detail, they merit a modest revision rather than a clean approval, even though no factual claim on the page was disputed.","score_delta":-5,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 2f0fef04-df9b-480a-8167-e2f3458a0e6a
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.