| Authors | Johnny Dilley; Andrew Poelstra; Jonathan Wilkins; Marta Piekarska; Ben Gorlick; Mark Friedenbach |
| Original submission | December 16, 2016 (arXiv v1); revised through January 30, 2017 (v3) |
| Length | 14 pages |
| Project | Liquid Network |
| License | No paper license is stated. arXiv’s non-exclusive distribution license is not an MIT content license. |
| Official source | Download the Strong Federations paper from Blockstream |
This page summarizes a technical paper for educational reference. It is not investment or legal advice. The original paper remains the source for its proposal; current Liquid documentation and incident reports describe later implementation and operations.
Johnny Dilley, Andrew Poelstra, Jonathan Wilkins, Marta Piekarska, Ben Gorlick, and Mark Friedenbach submitted “Strong Federations: An Interoperable Blockchain Solution to Centralized Third Party Risks” to arXiv on December 16, 2016. The paper presents Liquid as an early financial-market implementation of a federated Bitcoin sidechain, separating block-signing and peg-management roles while aiming to reduce settlement latency and hide transaction amounts and asset types. Its version history continued through January 30, 2017, so the original submission date and final listed revision date are different.
Why the Paper Proposed Strong Federations
The authors start from a practical trade-off. Bitcoin offers an open, proof-of-work network, but a transfer can take time to gain the confirmations that a business wants before treating it as settled. Its public ledger also exposes transaction activity for anyone to analyze. For market participants moving assets between venues, the paper argues that these properties can add settlement delay and reveal commercially sensitive information.
The paper’s answer is not a faster Bitcoin rule set. It proposes a separate sidechain whose operators are a known federation. Bitcoin is locked through a peg, and a corresponding asset can then move on the sidechain under its own consensus rules. That can support quicker transfers and confidential amounts, but it introduces a different trust model: users rely on the sidechain’s software and federation procedures as well as on Bitcoin for the locked coins.
How a Strong Federation Is Organized
The design separates two operator responsibilities. Blocksigners agree on and sign sidechain blocks. Watchmen observe the parent chain and participate in the transactions that move assets out of the sidechain. The paper’s rationale is that splitting these duties can limit the power of any one operator and make the system’s rules auditable. It does not mean the federation disappears or that users can force a withdrawal without its cooperation.
Liquid is built on Elements and has its own consensus process. Current Liquid documentation describes a federation with 15 functionary nodes; Blockstream’s 2026 incident assessment says at least 11 of the 15 must sign a block. A public full node can independently validate the Liquid chain, but validation does not grant the general public the ability to sign federation withdrawals. The published paper is a design document, so current operator counts and procedures should be read from current technical documentation rather than inferred from a 2016 description.
The Bitcoin Peg: Deposits, Withdrawals, and Trust
A federated peg connects Bitcoin and Liquid. For a peg-in, a user sends BTC to an address controlled by the federation and claims the corresponding LBTC on Liquid after the required Bitcoin confirmations. Current documentation specifies 102 confirmations, which averages about 17 hours at Bitcoin’s usual block interval. This delay is a security measure against deep Bitcoin reorganizations, not a Liquid block-time estimate.
A peg-out burns LBTC and requests BTC at a Bitcoin address. In ordinary operation, Liquid’s documentation describes processing in roughly 11 to 35 minutes, with timing dependent on network and federation conditions. That estimate is not a guarantee and is not applicable during a suspension. As of the latest detailed public recovery update located for this review—Liquid’s September 17, 2026 status—the network was processing transactions again while peg-outs remained paused during recovery. Check current notices from Liquid and your service provider before relying on a peg-in or peg-out.
Liquid should therefore be evaluated as a federated Bitcoin sidechain, not as a system that automatically inherits Bitcoin’s proof-of-work security. The federation and software govern the sidechain state and its connection to Bitcoin. A threshold signature can reduce dependence on a single signer, but it cannot make an incorrect state valid or guarantee that every operational process will behave safely.
Confidential Transactions and Their Limits
Liquid’s Confidential Transactions conceal transaction amounts from ordinary public observers while allowing nodes to verify commitments and proofs. Confidential Assets can also conceal which asset is being transferred. These features are intended to make amounts and asset types less visible on the public ledger; they do not make every part of a transaction private.
Addresses, transaction relationships, timing, and other public metadata can still reveal information. The sender and receiver need blinding information to view their own amounts, and a user can selectively share that information for auditing. Privacy therefore depends on how transactions and wallet data are handled, not merely on the presence of a confidentiality feature.
What the September 2026 Incident Shows
In its assessment of the September 6, 2026 incident, Blockstream attributed the exploit to a flaw in Elements’ range-proof verification cache. A cache entry was reused for a different output because the data used to identify the verification had an ambiguous serialization. That let an invalid transaction pass a check that should have rejected it and created approximately 4,000 LBTC without matching BTC backing. The failure was in Liquid/Elements validation; Bitcoin’s base-chain consensus was not changed.
Blockstream said the withdrawal went through SideSwap’s authorized peg-out path and that its Peg-out Authorization Key was not compromised. Its report also describes service-level controls that could have limited the impact, so the incident was not simply a story of a stolen signing key. The distinction matters: authorized signatures can still act on a state that software has incorrectly accepted.
Blockstream reports that 3,400 BTC were returned and that approximately 602 BTC remained outstanding in its September 2026 accounting. It says the invalid inflation was removed during recovery, block production resumed on a corrected chain, and user transactions resumed on September 10. Its latest detailed public status update located for this review, dated September 17, still said peg-outs were paused while recovery and testing continued. These are dated disclosures, not a claim that every service or peg is currently available.
The incident does not by itself establish that every federated sidechain will fail in the same way. It does show why the paper’s design claims must be considered alongside implementation correctness, review of consensus-critical code, signer procedures, service-level safeguards, and a credible recovery process. Hardware Security Modules can restrict key use; they cannot replace correct validation or guarantee against every software and operational failure.
Technical Snapshot
| Network model | Federated Bitcoin sidechain with separate Liquid consensus |
| Functionary threshold | Current incident report describes 11 signatures from 15 functionary nodes |
| Typical peg-in wait | 102 Bitcoin confirmations, about 17 hours on average |
| Typical peg-out timing | Normally about 11–35 minutes in current documentation; paused in the latest detailed September 17, 2026 recovery update found for this review |
| Confidentiality | Amounts and asset types can be hidden; transaction graph and metadata are not automatically private |
Social Media Sentiment
Discussion in a September 2026 r/Bitcoin thread about the incident focused on two questions: how a sidechain can have a valid threshold signature for a transaction that arose from invalid state, and what users must trust in a federation-controlled peg. Comments expressed both criticism of the model and attempts to distinguish a software-validation failure from compromised keys. This is a sample of discussion in one forum, not a representative survey of Liquid users or Bitcoin holders; some comments were speculative while the incident was still unfolding.
Last updated: 2026-10
Sources
- Dilley, J., Poelstra, A., Wilkins, J., Piekarska, M., Gorlick, B., & Friedenbach, M. (2016; revised 2017). “Strong Federations: An Interoperable Blockchain Solution to Centralized Third Party Risks.” Blockstream. The original design paper summarized above.
- arXiv. Record 1612.05491 for “Strong Federations.” Submission history and bibliographic record: first submitted December 16, 2016; version 3 dated January 30, 2017.
- arXiv. Non-exclusive distribution license. The repository’s right to distribute a submission is distinct from a statement that the paper is MIT-licensed.
- Liquid Developer Documentation. “Technical Overview.” Current explanation of Liquid’s functionaries, federation roles, and transaction model.
- Liquid Developer Documentation. “Peg-in and Peg-out.” Current confirmation and ordinary processing-time guidance.
- Liquid Developer Documentation. “Confidential Transactions.” Technical reference for Liquid transaction blinding and disclosure.
- Blockstream. “Liquid Network Security Incident Assessment.” September 2026 account of the range-proof cache exploit, recovery, and disclosed reserve impact.
- SideSwap. “SideSwap Markets Reopen with the Liquid Network.” SideSwap’s own dated account of its service status after the incident.