SubQuery

2026 is about turning infrastructure into usable intelligence. Our focus is on building: - Reliable network incentives - Advanced analytics & compute - Tools for builders & teams Full roadmap here → bit.ly/4ljZLhx

Power your apps with high-speed blockchain data using Traceye. 5X Faster Indexing, Lower Latency, Zero Maintenance. Build with Subgraphs or @SubQueryNetwork effortlessly. Start building today → Talk to an expert : traceye.io/?utm_source=tw…

Nobody brags about their indexer. Until it goes down. Then suddenly it’s the most important piece of the stack.

Try it yourself 👇 asksubquery.xyz

POV: You caught me browsing my favorite app

Try it out for yourself 👇 AskSubQuery.xyz

We asked three AI assistants a simple on-chain question: “What are the top 5 tokens on Uniswap by Token Value Locked?” ChatGPT is guessing ❌️ Claude doesn’t know ❌️ AskSubQuery just answers ✅️ The responses tell a bigger story about the current state of AI + blockchain data. • ChatGPT produced a confident, but incorrect, answer • Claude couldn’t access the data it needed • AskSubQuery returned the correct result instantly This isn’t about model quality. It’s about data access. Most AI tools still rely on static training data, scraped sources, or patchy APIs when it comes to blockchain queries. That means stale answers, guesswork, or no answer at all. AskSubQuery flips the model. It gives AI agents direct access to structured, indexed on-chain data in real time via GraphQL. No guessing. No hallucinations. Just verifiable answers. That’s the difference infrastructure makes. AI isn’t limited by intelligence anymore. It’s limited by access.

@DuSavior We'll be posting in ~8 hours time 😊

@SubQueryNetwork please post news asap

Update: All affected users have now been fully compensated. The recovery process is complete. Thanks to the community for your patience while we worked through this.

@Tha_Druid @0xGondarxyz @chrisdior777 Hmm I don't think we deleted our response? We were audited by Hacken. You can find full details of the incident in the report we released: x.com/SubQueryNetwor…

@0xGondarxyz @SubQueryNetwork @chrisdior777 why they deleted the reply

🚨JUST IN: @SubQueryNetwork EXPLOITED - $130K LOST setContractAddress() and setBatchAddress() in Settings.sol had zero access control. Any wallet could silently replace the protocol's core contract registry. After draining, attacker restored original addresses to cover tracks

@LindsayPoss Not me 🥹

can anyone name a protocol that hasn't had a major attack in like the past week because wtf is going on

@Isaaap4 Yes as mentioned in the tweet, all victims will be compensated the full SQT amount they lost.

@SubQueryNetwork Planean reembolsar los subquerry sustraidos de nuestras wallets?

A vulnerability in one of our contracts has been exploited. An immediate fix has been deployed, and the team is actively investigating other potential points of compromise. A total of 129,364,800 SQT was affected. We want to assure the community that all victims will be compensated in full. We are closely monitoring the situation and will provide further updates as more information becomes available. Thank you for your attention to this matter.

@GamerGwei_KR We've released a full report with these details now. Victims will be compensated in the next couple of days.

@SubQueryNetwork 129M SQT is no joke - how long until all victims are compensated?

@KKageCrypto Treasury

@SubQueryNetwork Are the refunds coming from treasury or insurance fund? 👀💰

We are continuing to investigate the recent exploit. For transparency, the primary attack transaction can be viewed here: basescan.org/tx/0xf23efa0fa… The staking contract has been impacted, and withdrawals will not be successful at this time. Functionality will be restored once the contract is fully refunded. We want to reiterate that all affected users will be compensated in full. We'll continue to share updates as more information becomes available.

@KKageCrypto It's outlined in the report, victims can expect compensation within the next couple of days.

@SubQueryNetwork How long until all 359M SQT is fully distributed back to victims? ⏰

We’ve published our full post-mortem on the recent security incident. The investigation identified an additional exploit, bringing the total impacted to 359,614,732 SQT. No private keys were compromised. Fixes are live, and all affected users will be fully compensated. Full details + recovery plan ↓ bit.ly/4syDr5M

@blockaid_ Two important pieces to note: - Our contracts were audited by two providers but with AI these days sophisticated attacks are possible - Victims will be compensated the full amount of SQT lost

🚨 Community Alert Blockaid's exploit detection system has detected an exploit on @SubQueryNetwork's SQT staking contract on Base, draining 218M SQT tokens ($128K). More details:

@leviathan_news Two important pieces to note: - Our contracts were audited by two providers but with AI these days sophisticated attacks are possible - Victims will be compensated the full amount of SQT lost

SubQuery staking contract exploited for $128K via unprotected setContractAddress function 🔗 x.com/SubQueryNetwor… 💬 leviathannews.xyz/redirect/22717… 🕵️ Benthic

@chrisdior777 Two important pieces to note: - Our contracts were audited by two providers but with AI these days sophisticated attacks are possible - Victims will be compensated the full amount of SQT lost

@biyun27666 Our staking contract was exploited so this was the result but we will be refunding the contract.

@SubQueryNetwork 质押的币都快归零了

@Normanrockon We had two audits done by different providers. For the attacker to access our staking contract was extremely sophisticated work - likely done with the help of AI which is why everyone should be doing a re-audit.

The root cause is they didn’t have any access control over setContractAddress() function, so anyone can just replace the contract address to the malicious one. This is an insanely easy bug that any security firm could find out. They just hadn’t done any. One time service is just not enough to protect protocols forever, time to have continuous verification.