Skip to main content
AVOID.NET
SubQuery Network3 decisions on this page

Audit log

Every state-changing event for SubQuery 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.

  1. #1publishby system:backfill
    2026-05-29 02:53:12Z
    Score: ?? (no score change)
    anchoranchored
    chain
    mainnet-betaslot 422,851,217
    sig
    WFfDMz2QtDzp…dTybj14qexplorer ↗
    hash
    8JaTx5x63Df2…spMjLSKZsha256 → base58
    verifying row…full verify ↗
    canonical bytes (5474 B) ▸
    {"actor":"system:backfill","investigation_id":"161be9c7-ee67-4ea2-9533-68617b497f21","kind":"publish","page_slug":"subquery-network","published_at":"2026-05-29T02:53:12.270Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"SubQuery Network","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://subquery.network/","type":"other","url":""},{"credibility":3,"name":"https://subquery.network/doc/subquery_network/token/token.html","type":"other","url":""},{"credibility":3,"name":"https://subquery.network/doc/subquery_network/introduction/introduction.html","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.crunchbase.com/person/sam-zou","type":"other","url":""},{"credibility":3,"name":"https://subquery.medium.com/leading-the-way-in-web3-meet-the-subquery-team-a49e40513b86","type":"other","url":""},{"credibility":3,"name":"https://subquery.medium.com/series-a-1abed6c1c2af","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://subquery.medium.com/subquery-raises-1-8m-seed-round-for-future-expansion-3348c1f2a931","type":"other","url":""},{"credibility":3,"name":"https://subquery.medium.com/series-a-1abed6c1c2af","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/price/subquery/vesting","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://subquery.medium.com/subquery-mainnet-and-sqt-launch-all-you-need-to-know-cd64186649f3","type":"other","url":""},{"credibility":3,"name":"https://blog.subquery.network/subquery-token-to-launch-on-bybit-exchange/","type":"other","url":""},{"credibility":3,"name":"https://cryptorank.io/price/subquery/vesting","type":"other","url":""},{"credibility":3,"name":"https://www.coingecko.com/en/coins/subquery-network","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/subquery-network/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://subquery.ghost.io/subquery-network-security-incident-report/","type":"other","url":""},{"credibility":3,"name":"https://subquery.network/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://hacken.io/audits/subquery-network/","type":"other","url":""},{"credibility":3,"name":"https://medium.com/@subquery/subquery-network-passes-smart-contract-audit-by-hacken-876a276fddeb","type":"other","url":""},{"credibility":3,"name":"https://subquery.ghost.io/subquery-network-security-incident-report/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://subquery.network/doc/subquery_network/token/token.html","type":"other","url":""},{"credibility":3,"name":"https://subquery.medium.com/series-a-1abed6c1c2af","type":"other","url":""}]}],"sources_used":[],"summary":"SubQuery Network is a Web3 data indexing protocol originally built for the Polkadot ecosystem, founded by Sam Zou and James Bayly out of New Zealand-based OnFinality. The project raised $10.8M in seed and Series A funding, launched its mainnet and SQT token in February 2024, and suffered a significant smart-contract exploit on April 12, 2026 in which a missing access-control modifier allowed an attacker to drain approximately 382 million SQT tokens (~$134,000 USD) from staker and delegator wallets across five transactions. ZachXBT flagged the entity in connection with this incident; the team published a full disclosure report and executed on-chain compensation for all affected wallets.","timeline":[{"date":"2021-01-01","event":"SubQuery raises $1.8 million seed round led by DeFi Alliance, D1 Ventures, Hypersphere Ventures, DFG, and The LAO.","source":""},{"date":"2021-09-11","event":"SubQuery announces $9 million Series A round co-led by Arrington Capital, DCG, and Stratos Technologies.","source":""},{"date":"2022-04-12","event":"SubQuery Network passes Hacken smart contract security audit with no material findings.","source":""},{"date":"2024-02-22","event":"SQT token deposits open on Bybit exchange ahead of mainnet TGE.","source":""},{"date":"2024-02-23","event":"SubQuery mainnet launches and SQT token begins trading on Bybit at approximately $0.0144.","source":""},{"date":"2024-03-29","event":"SQT reaches all-time high price of approximately $0.0855.","source":""},{"date":"2024-12-31","event":"SQT price ends 2024 approximately 76% below its launch price, trading around $0.005.","source":""},{"date":"2026-04-12","event":"Smart contract exploit on Base network drains approximately 382 million SQT (~$134,000 USD) from staking contract, 272 individual wallets, RewardsBooster, and Treasury via missing onlyOwner access control on the Settings contract setContractAddress() function.","source":""},{"date":"2026-04-13","event":"SubQuery team identifies full attack vector, simulates exploit traces, and deploys fix restoring onlyOwner modifiers to affected contract functions.","source":""},{"date":"2026-04-14","event":"On-chain compensation distribution begins; SubQuery publishes full public disclosure and recovery plan.","source":""},{"date":"2026-04-15","event":"On-chain compensation to all 272 affected staker and delegator wallets completed.","source":""}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision d000c40a-93d4-4b96-9a98-01eb6cd879c2
  2. #2reviewby reviewerreviewer
    2026-08-27 10:25:12Z
    Score: 5050 (no score change)
    This is a thin page (no section body text, only source lists, and an empty top-level sources_used array), so only 7 checkable atomic claims could be extracted, drawn almost entirely from the summary and timeline. The core narrative — founding, funding rounds, 2022 audit, and the April 2026 exploit mechanics and remediation — is well corroborated by SubQuery's own disclosures and independent sources. Two claims show internal or dating inconsistencies (a placeholder seed-round date and an ATH price that is correct in value but wrong in date, plus an internally inconsistent decline percentage), and the claim that ZachXBT flagged the incident could not be corroborated anywhere.
    anchoranchored
    chain
    mainnet-betaslot 443,525,155
    sig
    4gnbiRgpgLSk…NVPvCNHpexplorer ↗
    hash
    CvajtjbLd7d1…xqgjHQG7sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1034 B) ▸
    {"actor":"reviewer","decided_at":"2026-08-27T10:25:12.457Z","decision":"review","investigation_id":"161be9c7-ee67-4ea2-9533-68617b497f21","new_score":50,"page_slug":"subquery-network","prev_score":50,"reason":"This is a thin page (no section body text, only source lists, and an empty top-level sources_used array), so only 7 checkable atomic claims could be extracted, drawn almost entirely from the summary and timeline. The core narrative — founding, funding rounds, 2022 audit, and the April 2026 exploit mechanics and remediation — is well corroborated by SubQuery's own disclosures and independent sources. Two claims show internal or dating inconsistencies (a placeholder seed-round date and an ATH price that is correct in value but wrong in date, plus an internally inconsistent decline percentage), and the claim that ZachXBT flagged the incident could not be corroborated anywhere.","score_delta":0,"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 29965f6b-e8fb-4243-b4e7-f21d3bb71fb4
  3. #3review reviseby judgejudge
    2026-08-27 10:25:12Z
    Score: 5038 (-12)
    Recomputing from the claim_findings array (not the mismatched summary block) gives 4 confirmed, 2 partially_supported, 1 unverifiable, 0 disputed out of 7 claims, for a disputed_pct of (0+1)/7 = 14.3% — squarely in the 10-30% minor-issues band. The page's central material — SubQuery's founding, funding, its 2022 audit, and the April 2026 exploit mechanics and compensation — is confirmed against both the entity's own disclosure and independent analysis (claim_findings[0], [2], [4], [5]). Two claims carry dating and internal-arithmetic errors that were correctly kept out of the numerator as partially_supported rather than disputed (claim_findings[1]'s seed-round date, claim_findings[3]'s ATH date and its 76%-vs-65% decline inconsistency). The one claim driving the disputed_pct is claim_findings[5], an unverifiable attribution crediting ZachXBT with flagging this incident — the reviewer found no supporting source anywhere, including ZachXBT's own archive, and 'unverifiable' rather than 'disputed' is the correct call since absence of corroboration is not a contradicting source. That single claim names a real individual in an attribution nobody can substantiate, which is why the delta sits at the harsher end of the minor-issues band despite the low sample size and the reviewer's own reduced confidence (0.65).
    anchoranchored
    chain
    mainnet-betaslot 443,525,159
    sig
    4VUbH9ts1PZ1…unTE6oo5explorer ↗
    hash
    BBguuM4irFPD…LH5EJFELsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1683 B) ▸
    {"actor":"judge","decided_at":"2026-08-27T10:25:12.457Z","decision":"review_revise","investigation_id":"161be9c7-ee67-4ea2-9533-68617b497f21","new_score":38,"page_slug":"subquery-network","prev_score":50,"reason":"Recomputing from the claim_findings array (not the mismatched summary block) gives 4 confirmed, 2 partially_supported, 1 unverifiable, 0 disputed out of 7 claims, for a disputed_pct of (0+1)/7 = 14.3% — squarely in the 10-30% minor-issues band. The page's central material — SubQuery's founding, funding, its 2022 audit, and the April 2026 exploit mechanics and compensation — is confirmed against both the entity's own disclosure and independent analysis (claim_findings[0], [2], [4], [5]). Two claims carry dating and internal-arithmetic errors that were correctly kept out of the numerator as partially_supported rather than disputed (claim_findings[1]'s seed-round date, claim_findings[3]'s ATH date and its 76%-vs-65% decline inconsistency). The one claim driving the disputed_pct is claim_findings[5], an unverifiable attribution crediting ZachXBT with flagging this incident — the reviewer found no supporting source anywhere, including ZachXBT's own archive, and 'unverifiable' rather than 'disputed' is the correct call since absence of corroboration is not a contradicting source. That single claim names a real individual in an attribution nobody can substantiate, which is why the delta sits at the harsher end of the minor-issues band despite the low sample size and the reviewer's own reduced confidence (0.65).","score_delta":-12,"sequence_num":3,"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 16627869-b744-4648-983c-db426c51e476
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>.