SQD has added validated data from 10 blockchain networks to Google Cloud’s BigQuery platform, giving developers and companies access to full chain histories checked through six cryptographic tests.

SQD brings validated blockchain data into BigQuery

SQD said in an Aug. 24 announcement that its enterprise arm, SQD 360, is providing the indexing system and data pipelines behind datasets available through Google Cloud Web3 Blockchain Analytics.

The initial contribution covers 10 networks from their genesis blocks, allowing analysts to examine their complete available histories rather than records collected only after the integration began. SQD did not identify all 10 chains in its announcement or provide a timetable for adding the next group.

Before the information reaches BigQuery, SQD said each block passes six cryptographic checks. The process includes comparing data from multiple sources and checking transaction roots and state roots, which are cryptographic values used to confirm whether a block’s records match the underlying blockchain state.

SQD said the checks are intended to catch missing, incorrect, or inconsistent records before they enter analytics pipelines. Fresh blocks must also pass the validation process as the datasets continue to update.

Once loaded into BigQuery, the records become available through the same cloud environment used for business intelligence, machine learning, and large-scale data analysis. Developers can therefore examine blockchain activity without building an indexer, storing an entire chain history, or maintaining separate infrastructure for each network.

“Partnering with Google Cloud Web3 to bring our validated data standard to BigQuery is a defining step for SQD, and a strong signal that enterprise-grade blockchain data has arrived,” SQD CEO Wanja Oberhof said.

The companies did not disclose financial terms, revenue-sharing arrangements, or service-level commitments tied specifically to the partnership.

SQD Network distributes storage and query work

SQD operates a decentralized data network built to collect, verify, store and serve information generated by blockchains and Web3 applications. Its infrastructure separates the work among data providers, independent worker nodes, and gateways rather than relying on one central database.

According to SQD Network documentation, data providers submit blockchain records before a scheduler assigns pieces of each dataset to worker nodes. Workers supply storage and computing resources, hold copies of the assigned records, and answer queries submitted through gateways.

Each worker must bond 100,000 SQD tokens to register on the network. Workers receive token rewards based on factors such as uptime, the amount of data served, and delegated tokens, while provable violations of network rules can lead to penalties.

Gateways provide the connection between data consumers and the worker network. The amount of SQD locked by a gateway operator determines how many requests it can send, tying query capacity to the network’s token-based resource system.

SQD says its full data service covers more than 130 networks, although only 10 are included in the first Google Cloud contribution described in the announcement. Its Portal product offers historical and real-time information from chains across the Ethereum Virtual Machine, Solana, Substrate, and Bitcoin-based ecosystems.

Unlike a standard blockchain node, which may provide raw or recent network information, SQD’s system converts records into structured datasets containing blocks, transactions, logs, traces and changes in blockchain state. Structured records allow analysts to search large periods and compare activity without processing raw chain files each time.

Google Cloud expands access to indexed onchain records

Google Cloud describes Blockchain Analytics as a service that places indexed blockchain information in BigQuery for analysis through SQL, a common language for searching and organizing databases. The product lets users query blocks, transactions, event logs, and call traces without operating nodes or creating an indexer for every protocol.

BigQuery can also combine onchain records with a company’s internal data. A wallet service, for example, could compare blockchain transactions with activity recorded inside its application, while a compliance team could build searches for transfers involving specified addresses. The accuracy of any resulting report would still depend on the query design, address labels, and other data added by the user.

Google Cloud began placing blockchain records in BigQuery in 2018 with Bitcoin and later added Ethereum and other networks. In 2023, the company added 11 blockchain datasets, including Avalanche, Arbitrum, Optimism, Polygon, Polkadot, and Tron.

The SQD arrangement follows other efforts to connect decentralized data sources with cloud services. In July 2025, crypto.news covered OORT’s dataset listing on Google Cloud Analytics Hub and several other enterprise marketplaces. OORT’s offering contained 100,000 user-contributed data points, with their contributions recorded onchain to help users check the source and structure of the information.

Google Cloud has also built services that give applications direct access to blockchain networks. In September 2024, it launched an Ethereum RPC that initially supported the Ethereum mainnet and test networks. The preview offered a free tier of up to 100 requests per second and one million requests per day.

The RPC service and BigQuery datasets serve different tasks. RPC endpoints allow applications to request current blockchain information and submit transactions, while indexed datasets are designed for searches across large amounts of historical data.

BigQuery data supports enterprise and agent-based analysis

For U.S. developers and companies already using Google Cloud, the integration places SQD-supplied records inside a familiar analytics service rather than requiring a separate blockchain-data system. Google’s documentation says users can reach public datasets through the Cloud console, command-line tools or the BigQuery API.

Google pays the storage costs for datasets included in its Public Dataset Program, while users pay for the queries they run. The first one terabyte of query processing each month is free under Google Cloud’s current pricing structure, although access can be limited by an organization’s own security controls.

Dataset location also matters for American users, with internal policies governing where information is processed. Google says every public dataset has an assigned region, while its BigQuery sample tables are held in the U.S. multi-region. SQD’s announcement did not specify the storage location for each contributed blockchain dataset.

Agent-based access forms another part of the planned work. In May, earlier coverage reported that Solana Foundation and Google Cloud launched Pay.sh, which lets AI agents pay for APIs with stablecoins and supports services including BigQuery, Gemini and Vertex AI.

Under the SQD roadmap, additional agent functions could allow automated software to retrieve and analyze verified blockchain records inside Google Cloud. SQD did not explain which functions will be released, which AI systems will support them, or when they will become available.

More blockchain networks are also due to join the integration, according to the announcement. SQD has not named the next chains, disclosed how they will be selected, or provided a release schedule.

Bitwise Asset Management has launched automated portfolios of Coinbase’s tokenized US stocks that allow eligible investors outside the United States to follow preset investment strategies while keeping the assets in their own wallets.

The portfolios use Coinbase’s recently launched tokenized stocks, while Glider automatically rebalances users’ holdings to match model portfolios designed by Bitwise, according to a Tuesday announcement.

The initial lineup includes three strategies — the Mag7X, robotics and AI leaders — and include Apple, Nvidia, Microsoft, Tesla and SpaceX.

Tokenized listed stocks now total $2.49 billion, up 5.18% over the past month, with 2.25 million holders and $27.28 billion in monthly transfer volume, according to rwa.xyz.

Unlike a traditional fund, the tokenized stocks remain in users’ non-custodial wallets, with Bitwise setting the portfolio methodology and Glider handling trades and rebalancing. Bitwise charges a 0.15% methodology access fee, excluding trading and Glider platform fees.

Because users retain the individual tokens, Bitwise said the assets could also be used in DeFi applications for lending or borrowing, subject to the risks of those protocols.

The launch comes a day after Coinbase’s tokenized US stocks went live on Base, allowing eligible non-US users to trade the assets around the clock and use them across DeFi applications.

Magazine: MiCA is coming for DeFi vaults, but regulation will be difficult

Cointelegraph is committed to independent, transparent journalism. This news article is produced in accordance with Cointelegraph’s Editorial Policy and aims to provide accurate and timely information. Readers are encouraged to verify information independently.

World Liberty Financial has rolled out its USD1 stablecoin natively on the Canton Network, positioning the token as a “cash leg” for settlements that pair stablecoin liquidity with tokenized real-world assets (RWAs). The company says the move is designed for institutional use cases where the stablecoin can sit alongside tokenized assets within the same transaction, including scenarios involving derivatives collateral, lending, and issuance and redemption flows.

According to a Tuesday announcement, USD1 is now issued and managed through the Canton integration with privacy and permissioning controls provided by the network. World Liberty adds that the design supports native issuance, allowing USD1 to be used directly in settlement rather than requiring institutions to rely solely on external exchanges or offchain routing.

Key takeaways

• World Liberty Financial launched USD1 natively on Canton to support institutional settlement alongside tokenized RWAs in the same transaction.
• USD1’s use cases span derivatives collateral, institutional lending, and RWA asset issuance and redemptions.
• The stablecoin’s market capitalization is about $4.05 billion, making it the sixth-largest stablecoin by DeFiLlama data.
• USD1 is issued and managed with reserves and mint/redemption processing handled by BitGo Bank & Trust, per World Liberty.
• The integration comes after additional Canton expansion plans, including a pilot connected to state-administered benefits distribution.

Why native USD1 on Canton matters for RWA settlement

For institutional finance, the key constraint in many tokenized-asset workflows is coordinating “cash” and “asset” legs efficiently and with appropriate governance. World Liberty’s announcement frames USD1 on Canton as a solution to this coordination problem: institutions can use USD1 directly for settlement that involves tokenized RWAs while simultaneously applying Canton’s permissioning and privacy features.

The company specifically highlights transaction categories where this structure is expected to be useful. In addition to serving as cash for tokenized asset transfers, USD1 is positioned for derivatives collateral, institutional lending, and the issuance and redemptions of tokenized assets. In practice, these are exactly the kinds of operations where onchain programmability needs to meet operational requirements typically associated with traditional settlement systems.

USD1 supply, reserves, and the role of BitGo Bank & Trust

USD1 has a market capitalization of about $4.05 billion, according to DeFiLlama’s stablecoin data, where it ranks as the sixth-largest stablecoin. That size matters because it suggests the token already has meaningful liquidity and visibility—two factors that institutions often consider when deciding whether a stablecoin can be operationally relied upon for settlement.

World Liberty states that USD1 is issued by BitGo Bank & Trust, which manages the stablecoin reserves and processes mints and redemptions. For readers assessing counterparty and operational risk, this is a notable detail: the integration is not simply a “token move” to a new chain, but a placement of USD1’s core issuance and redemption workflow into a Canton-based settlement environment.

When USD1 launched earlier, World Liberty said it was backed by reserves that include short-term U.S. Treasurys, government money market funds, and dollar deposits. The company’s current Canton deployment continues to emphasize the stablecoin’s use in institutional settlement rather than introducing a new asset class or altering the stated reserve backing in the announcement.

Canton’s institutional framing and network claims

Canton is described by the network as a public, permissionless blockchain intended for institutional finance. In the announcement, Canton’s positioning centers on scale and real-world asset throughput: the network claims it processes and issues more than $9 trillion in tokenized assets each month, and it reports moving more than $350 billion in onchain U.S. Treasurys daily.

Whether institutions focus on the specific magnitude of those figures or not, Canton’s broader pitch is consistent—enabling financial institutions to connect tokenized assets with settlement rails that can fit into regulated workflows. World Liberty’s move to list USD1 natively on Canton is aligned with that pitch: instead of treating the stablecoin as a separate settlement instrument that must be bridged or swapped, the integration targets same-transaction settlement behavior.

What’s next: Canton expansion and RWA distribution experiments

The USD1 launch on Canton follows another Canton expansion announcement made last week. In that update, Digital Asset and former U.S. House Speaker Paul Ryan’s American Idea Foundation described plans for a Canton-based system intended to distribute state-administered benefits across three U.S. states beginning in 2027.

That parallel matters for investors and builders because it suggests Canton is pursuing both “market infrastructure” goals—like RWA and treasury settlement—and “public services” applications that require operational controls. If these tracks progress, networks and stablecoin issuers tied to Canton could see increased relevance in institutional settlement flows beyond financial derivatives and lending.

Still, readers should watch how quickly institutions adopt the integrated settlement design. The announcement explains the capability at launch and ties it to established USD1 issuance and reserve processes, but it does not specify which institutions are actively using the new settlement path or what volumes are expected in the near term.

For now, the practical question is whether native USD1 settlement on Canton becomes a repeatable rails-choice for tokenized RWA operations—especially in lending, collateral management, and issuance/redemption cycles—while Canton’s broader institutional and benefits-distribution initiatives move from planning into execution.

Tributes