Blockstream launched Liquid as a federated Bitcoin settlement network

Blockstream puts Liquid into production

On October 10, 2018, Blockstream announced the launch of Liquid, a federated Bitcoin sidechain designed for settlement among cryptocurrency exchanges, market makers, brokers and other institutions. The company said the production blockchain had actually gone live on September 27, 2018, at 1:29 UTC. It named 23 launch members, including Bitfinex, BitMEX, OKCoin, Xapo, SIX Digital Exchange and Zaif.

That chronology matters. October 10 was the public launch announcement, while September 27 was the reported network activation. The development was consequential because it put a long-discussed sidechain design into commercial operation with a group of recognizable trading venues. It did not change Bitcoin's consensus rules.

What Liquid was built to do

Moving bitcoin between exchanges on the Bitcoin blockchain can require participants to wait for multiple confirmations before treating a deposit as settled. Trading firms can instead keep balances at several venues, but that fragments capital and adds exposure to each venue. Liquid offered a separate settlement ledger intended to move a bitcoin-linked asset between participating institutions more quickly.

Under the design described by Blockstream, bitcoin moved into the system through a two-way peg and was represented on Liquid as L-BTC. The company said L-BTC could be redeemed for bitcoin and claimed full settlement in two minutes. Liquid also supported issued assets and Confidential Transactions, which were designed to conceal transferred amounts and asset types from outside observers while leaving transactions verifiable under the network's rules.

Those were product and design claims on October 10, not independent measurements of production throughput, liquidity or adoption. Blockstream's announcement supplied no transaction-volume series, value-locked figure, service-level history or comparison measured over a defined operating window.

The federation was the central trade-off

Liquid did not use Bitcoin's open proof-of-work mining process to order its blocks. Its “Strong Federation” model assigned two critical jobs to a defined group of functionaries: blocksigners advanced the sidechain ledger, and watchmen controlled transfers back to the Bitcoin blockchain under preset rules.

Blockstream's January 6, 2017 technical paper called the approach distributed and publicly verifiable but “not fully decentralized.” The paper also described Liquid's trust model as weaker than Bitcoin's, even as it argued that geographic and jurisdictional distribution could avoid reliance on one operator. That distinction was essential to evaluating the launch. Liquid traded some of Bitcoin's permissionless participation and proof-of-work security model for faster, more predictable settlement among identified operators.

Contemporaneous reporting from CoinDesk confirmed the 23-member launch and highlighted the same caveat: the deployed system was a federated sidechain, not the trust-minimized sidechain model some Bitcoin developers originally envisioned. Anyone assessing the announcement therefore had to separate “sidechain” as a technical category from an assumption that Liquid inherited every security property of Bitcoin.

Why the launch mattered

The launch represented a concrete institutional use of Bitcoin-adjacent infrastructure during a period when exchanges remained fragmented and transfers between venues could constrain arbitrage and liquidity management. It also showed one route for adding confidential transfers and token issuance without modifying Bitcoin's base layer.

The narrower conclusion is the defensible one. On October 10, 2018, Liquid was a live, member-operated settlement network with 23 announced participants and integrations still to be completed. The primary record verified the launch, design and participants; it did not establish broad usage, lower spreads, improved prices or the absence of operational and custody risk. No price or market-performance claim is made here because the cited records do not provide a venue-specific, time-bounded dataset from which to test market impact.