SQD

What is SQD?

SQD, formerly Subsquid, is a decentralized blockchain data network that stores, validates, and serves historical on-chain data through a distributed data lake and query engine rather than requiring developers to run full archive nodes or depend on centralized RPC and API vendors.

Its core problem is not transaction settlement but data availability for applications, indexers, analytics systems, AI agents, and compliance workflows that need fast access to historical blockchain state across many chains.

The project’s claimed moat is architectural: worker nodes store compressed data chunks, Portal streams the data to applications, and the system uses cryptographically verifiable, immutable Parquet records rather than a single managed database behind an API key, positioning SQD as infrastructure for high-volume indexing rather than a consumer-facing Layer 1 asset. The project describes the network as covering more than 200 chains and serving data through a decentralized access layer, while third-party market trackers in mid-June 2026 placed SQD in the mid-cap infrastructure-token category rather than among top Layer 1 or DeFi assets, with rankings fluctuating around the high-400s depending on source methodology and circulating-supply treatment. SQD Network documentation (docs.sqd.dev) CoinMarketCap SQD profile (coinmarketcap.com)

SQD’s market position is best understood as niche-but-relevant middleware. It is not a general-purpose smart-contract platform, does not have a native DeFi TVL comparable to Ethereum, Solana, or Arbitrum, and should not be analyzed as if deposits into SQD contracts represent an application economy. Its “TVL relevance” is indirect: the company has stated that protocols using its infrastructure collectively represent more than $15 billion in combined TVL, but that is customer exposure, not value locked in SQD itself. The more meaningful usage indicators are network capacity, query volume, data served, and the number of independent workers. SQD’s own materials show a scale-up from 811 online workers and 594 TB stored in a July 2024 roadmap post to more than 2,000 worker nodes and petabyte-scale data by 2026; its February 2026 revenue-pool update reported 4.6 million queries over 24 hours and 424.68 million over 90 days, while later corporate materials cited roughly 5 million queries per day. Those figures indicate real infrastructure usage, but they remain project-reported metrics rather than independently audited active-user counts. SQD 2024 roadmap (sqd.dev) SQD sustainable rewards update (sqd.dev) Rezolve acquisition announcement (sqd.dev)

Who Founded SQD and When?

Subsquid emerged in 2021, during the period when DeFi, NFTs, and appchain ecosystems created heavy demand for blockchain indexing beyond what ordinary RPC endpoints could economically support. The project is commonly associated with Dmitry Zhelezov and Marcel Fohrmann, with Zhelezov serving as a technical co-founder and later CTO in the post-acquisition structure, while Fohrmann became CEO of SQD after the project’s acquisition by Rezolve Ai. The corporate issuer and early development entity was Subsquid Labs GmbH, and the token documentation describes SQD as an ERC-20 protocol token used to coordinate worker rewards, delegation, network access, and governance. The project’s economic launch context matters: it was not born into a risk-free capital environment, but into a market where venture-backed Web3 infrastructure projects were competing to replace centralized node providers while developers were still relying heavily on hosted subgraphs, RPC endpoints, and warehouse-style analytics products. CoinMarketCap SQD profile (coinmarketcap.com) SQD tokenomics documentation (docs.sqd.ai)

The project’s narrative has shifted materially.

Early Subsquid was primarily framed as an indexing stack for Substrate and later multichain developers; by 2024 it was repositioning toward a broader decentralized data lake, light indexers, data streams, SQL-style querying, and query verification.

In October 2025, Rezolve Ai announced the acquisition of Subsquid, presenting SQD as the data layer in a larger “agentic commerce” stack combining blockchain data, AI systems, and digital-asset payments.

That acquisition did not change the stated utility of the SQD token, but it did change the project’s strategic center of gravity: SQD is now partly a decentralized infrastructure network and partly a data asset inside a Nasdaq-listed company’s AI-commerce narrative.

That dual identity is potentially valuable for distribution but also introduces execution and governance complexity, especially because the SQD team has stated that a token rebrand remains subject to regulatory and exchange approvals. Rezolve acquisition announcement (sqd.dev)

How Does the SQD Network Work?

SQD is not a Layer 1 consensus blockchain and does not use a conventional PoW or PoS consensus mechanism for block production. It is better classified as a decentralized data-infrastructure network whose economic coordination and settlement functions rely on ERC-20 smart contracts, with Arbitrum used for many network operations and SQD also bridged or deployed across chains including Base, Arbitrum One, and BNB Smart Chain according to the asset contract data. The network architecture consists of data providers, persistent storage, a scheduler, workers, gateways or Portals, logs collectors, validators, reward managers, and on-chain registries. Data providers ingest blockchain data, validate it by comparing hashes, split it into compressed chunks, and make it available for workers; workers contribute storage and compute, serve data peer-to-peer, and commit signed logs of executed requests. This is closer to a decentralized storage-and-query market than to a chain that reaches consensus over arbitrary state transitions. SQD whitepaper (docs.sqd.dev)

The distinctive technical design is modularity around data access rather than execution. SQD stores historical blockchain data as immutable Parquet files, replicates data across worker nodes, and exposes it through Portal, a streaming access layer intended to let applications query multiple blocks and granular data ranges more efficiently than conventional RPC. The roadmap has included data streams, SQL query functionality, decentralized dataset provisioning, and query validation using cryptographic verification methods, including planned ZK and TEE options described in earlier roadmap materials. Workers must bond SQD to register, can be slashed for provable protocol violations, and receive rewards based on liveness, amount of data served, delegation, fairness, and query logs. A 2026 ChainSecurity assessment covered smart-contract components such as staking, worker registration, reward treasury, gateway registry, and reward distribution, but the report also states the standard limitation that audits do not guarantee absence of vulnerabilities. SQD Network page (sqd.dev) SQD roadmap (sqd.dev) ChainSecurity audit (reports.chainsecurity.com)

What Are the Tokenomics of SQD?

SQD has a fixed initial supply schedule rather than an immediately open-ended inflation model. Public market trackers in June 2026 reported a maximum supply of about 1.337 billion SQD and a circulating supply above one billion tokens, while the official tokenomics page breaks allocation into backers, team, treasury, worker rewards, community sale, and testnet incentives.

The largest official buckets are reserved treasury at 28.1%, seed and pre-seed backers at 28.3% combined, team at 15%, worker rewards at 10%, liquid treasury at 5%, community sale at 5%, strategic backers at 6.6%, and testnet-related allocations at 2%.

Vesting schedules vary by category; for example, worker rewards vest over 84 months, the reserved treasury over 36 months after TGE, and several investor and team allocations combine a six-month lockup with partial release and linear vesting.

This means SQD’s float has been expanding through unlocks even if the initial supply cap is fixed, so investors should distinguish “maximum supply” from practical sell pressure. SQD tokenomics documentation (docs.sqd.ai) CoinMarketCap SQD profile (coinmarketcap.com)

The token’s value accrual model is utilitarian but not mechanically equivalent to gas on an L1. SQD is used to reward worker nodes, delegate to workers, curate reliable infrastructure, participate in governance, and lock for higher data-access capacity. Each worker registration requires a 100,000 SQD bond under the whitepaper model, and delegators can assign SQD to workers to earn a share of rewards without running hardware. During the initial three-year bootstrapping phase, rewards are funded from a pool equal to 10% of supply, with caps designed to prevent excessive distribution; after that phase, future issuance is expected to be subject to governance rather than fixed forever at launch.

A major 2026 tokenomics development was the beta launch of Portal Revenue Pools, where SQD holders may lock tokens behind Portals serving paying demand and receive USDT-denominated rewards from Portal fees, with the project stating that up to 50% of fees may flow to independently managed pools while the remainder supports network incentives and long-term supply management.

This is a more credible value-accrual narrative than pure emissions, but it is still early and depends on sustained paying demand rather than tokenholder circularity. SQD whitepaper (docs.sqd.dev) SQD Revenue Pools update (sqd.dev)

Who Is Using SQD?

SQD usage should be separated from speculative trading. Exchange listings, daily volume, and mid-cap token ranking show market attention, but the infrastructure case rests on whether developers and enterprises actually query the network. SQD’s reported production usage is concentrated in DeFi, analytics, AI agents, wallets, payments, compliance, and data-heavy indexing workloads. Its own materials cite millions of daily queries, petabytes of indexed or served blockchain data, and hundreds of supported networks; those figures are directionally consistent with infrastructure adoption but should be treated as company-reported operating metrics rather than neutral on-chain active-address data.

The network’s user base is therefore not ordinary wallets transacting with a dApp; it is developers, protocols, gateways, data consumers, and node operators. That distinction is important because a data network can have low visible wallet activity while still handling meaningful backend traffic. SQD Network page (sqd.dev) SQD sustainable rewards update (sqd.dev)

The most visible institutional development is Rezolve Ai’s October 2025 acquisition of Subsquid, which tied SQD to a Nasdaq-listed AI-commerce company and its broader retail, payments, and agentic-commerce strategy. In May 2026, Rezolve announced that SQD had gone live on Revolut, giving the token distribution through a mainstream fintech interface rather than only crypto-native exchanges; Rezolve also stated that SQD continued to trade on major exchanges including Coinbase, Binance, and Bybit. For enterprise adoption, SQD’s own website references use cases across DeFi and trading, analytics, AI agents, wallets and payments, compliance, stablecoins, and RWA, but the analyst should avoid treating every logo or sector page as audited revenue. The most defensible statement is narrower: SQD has moved beyond a pure developer-tool project into a corporate distribution channel through Rezolve, while its durable adoption will depend on whether paying Portal customers scale faster than token emissions and infrastructure costs.

Rezolve SQD Revolut announcement investor.rezolve.com Rezolve acquisition announcement (sqd.dev)

What Are the Risks and Challenges for SQD?

SQD’s regulatory status is not equivalent to Bitcoin or Ether, and there is no spot ETF narrative or commodity-style regulatory consensus around the asset. Research did not identify a publicly announced active enforcement lawsuit specifically against SQD as of June 2026, but absence of a visible lawsuit is not the same as legal certainty. The issuer has prepared a MiCA token white paper for EU/EEA trading-platform admission, and project communications have explicitly noted that a token rebrand is planned only subject to regulatory and exchange approvals. U.S. classification risk remains a general risk for utility tokens with investor allocations, staking rewards, governance claims, and corporate promotion, particularly after the Rezolve acquisition made SQD more visible to public-market investors.

Centralization risk is also non-trivial: the whitepaper states that during the bootstrapping phase Subsquid Labs GmbH acts as the sole data provider proxy, data-provider expansion depends on governance and trusted parties, and several operational components such as reward submission and dataset management rely on structured roles rather than fully autonomous decentralization from day one. SQD MiCA white paper (cdn.sqd.ai) SQD whitepaper (docs.sqd.dev) Rezolve acquisition announcement (sqd.dev)

The competitive risk is severe because blockchain data is a crowded infrastructure segment.

SQD competes against decentralized indexing protocols such as The Graph, managed indexing and pipeline providers such as Goldsky, unified API vendors such as Covalent, and large centralized infrastructure providers such as Alchemy, QuickNode, and internal data teams at exchanges, funds, and major protocols. The Graph remains the category reference for decentralized indexing, while Goldsky and Covalent compete on developer convenience, multichain coverage, and enterprise reliability. SQD’s differentiation is its decentralized data lake, worker model, Portal streaming API, and revenue-pool design, but developers are pragmatic: they will choose the cheapest, fastest, most reliable stack that minimizes engineering risk. If centralized vendors deliver adequate uptime and latency at lower integration cost, or if The Graph and commercial indexers absorb the same AI-agent and analytics demand, SQD’s tokenized infrastructure model could face margin compression despite technically credible architecture. The Graph indexing docs (thegraph.com) Goldsky docs (docs.goldsky.com) Covalent API profile (postman.com)

What Is the Future Outlook for SQD?

SQD’s near-term outlook depends less on token price and more on whether it can convert technical capacity into durable, fee-paying demand. Verified roadmap and recent operating items include Portal Revenue Pools in beta from early 2026, public-gateway API-key requirements effective May 2026, tooling updates for MCP and Substrate parity, continued work on SQL-style querying, self-hosted Portal, private and structured datasets, and AI-agent access to Portal APIs.

The April 2026 pricing update for SQD Cloud, including higher hosting and RPC add-on pricing, also suggests the project is trying to normalize commercial infrastructure economics rather than subsidize usage indefinitely.

The structural hurdle is that SQD must prove decentralization, correctness, and cost efficiency simultaneously: too much central coordination weakens the Web3 thesis, too much decentralization can degrade enterprise reliability, and too much token incentive can obscure whether demand is organic. SQD changelog (docs.sqd.dev) SQD pricing update (docs.sqd.dev) SQD Network roadmap page (sqd.dev)

The sober infrastructure case for SQD is that blockchain data volumes are rising faster than most application teams’ willingness to operate archive nodes, and AI agents, compliance systems, trading desks, and DeFi protocols need structured historical data more than they need another execution chain.

The skeptical case is that data infrastructure is hard to defend economically because customers are latency-sensitive, price-sensitive, and willing to use centralized vendors when the trust assumptions are acceptable. SQD’s future therefore turns on measurable adoption of Portal, revenue-backed staking, enterprise retention after the Rezolve acquisition, and the execution of verification and self-hosting milestones. No price prediction is warranted; the relevant question is whether SQD becomes a revenue-producing neutral data layer or remains a technically interesting tokenized indexer competing in a market where developer convenience often beats decentralization purity.