Deep Dive
1. Portal + Pipes SDK Upgrade (November 2025)
Overview: Touted as the network's "largest upgrade," this development focused on the Portal and Pipes SDK (helloSQD). The goal was to enhance the core infrastructure for developers building on Subsquid, likely improving how data is indexed, queried, and delivered across its decentralized data lake.
What this means: This is bullish for SQD because it directly improves the utility and performance of the network for developers, which is essential for driving adoption. Successful upgrades can strengthen Subsquid's competitive position against other indexing services like The Graph.
2. Institutional Phase & Strategic Shift (June 2026)
Overview: In June 2026, Subsquid announced it was "entering its institutional phase" with a new CEO and board (helloSQD). The stated focus is to become the obvious choice for institutions seeking on-chain data, leveraging its existing scale of serving 1.4 petabytes of data daily.
What this means: This is bullish for SQD because pivoting to serve institutional demand could open significant new revenue streams and validate the network's enterprise-grade capabilities. However, it is also a neutral-to-risky shift as it depends on execution and competing in a crowded data infrastructure market.
3. Post-Acquisition Integration & Growth (Ongoing)
Overview: Following its acquisition by Rezolve Ai in October 2025 (Decrypt), Subsquid's roadmap involves integrating into a broader AI and payments stack. Rezolve plans annual treasury acquisitions of SQD tokens, tying token demand to its revenue.
What this means: This is bullish for SQD because it provides financial backing and a clear demand driver through treasury buys. The integration aims to make Subsquid's data crucial for AI-powered commerce, potentially increasing its utility and token velocity.
Conclusion
Subsquid's trajectory is defined by a strategic pivot to institutional markets and deeper integration into the AI data economy post-acquisition. How effectively will the network balance developer-centric upgrades with the demands of large-scale institutional clients?