# How does the Liquid Federation's multisig work? Source URL: https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/how-does-the-liquid-federations-multisig-work Updated: 2026-04-09T09:37:52.000Z Category: Liquid Network Section: FAQs --- The Liquid Federation uses an 11-of-15 multisig wallet to process [peg-ins](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-peg-in) and [peg-outs](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-peg-out) and secure bitcoin held in the federation wallet. Additional [timelocks](https://glossary.blockstream.com/timelocks/) are used to provide an [emergency withdrawal procedure](#h%5F01EGTTXQCPGEH19Z3FFKZJ3ZSV). ## Peg-Ins During [the peg-in process](https://helpcenter.dxp-frontend.devserver.app/liquid-network/perform-advanced-liquid-operations/peg-in-btc-to-the-liquid-network), a user sends bitcoin to an [address](https://glossary.blockstream.com/address-bitcoin/) secured by the federation’s 11-of-15 multisig. The 15 [Liquid functionaries](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-are-the-different-types-of-participants-in-the-liquid-network) each hold one key, which is stored in their specialized HSM hardware. The high key threshold for the federation's multisig wallet provides a high level of [Byzantine fault tolerance](https://en.wikipedia.org/wiki/Byzantine%5Ffault): compromising the wallet’s multisig functionality would require at least five functionaries to stop operating at the same time. Functionaries are operated by incorporated cryptocurrency companies that are known to each other and distributed around the world. They have economic incentives to operate the functionaries in the network’s best interest. Therefore the possibility of a scenario where a large portion of the federation simultaneously stops operating is very low. ## Peg-Outs When a Liquid Federation member performs a peg-out, the federation functionary units verify that the peg-out transaction has been sent to a whitelisted address (PAK list) and the corresponding amount of LBTC has been burned by the member performing the peg-out. Then, using 11 of the federation’s 15 multisig keys (held on the functionary HSMs) the federation signs the peg-out transaction. ## Emergency Withdrawal Procedure In addition to multisig, the federation’s wallet implements an Emergency Withdrawal Procedure (EWP) by using timelocks. A timelock is a smart contract feature implemented at the Bitcoin protocol-level that disables bitcoin from being spent according to certain conditions until a specified point in time or [block height](https://glossary.blockstream.com/block-height/). In Liquid, after the expiry of a timelock, a set of emergency backup keys can be used to spend the associated bitcoin (in addition to the regular 11-of-15 multisig keys). This ensures that the funds in the federation wallet cannot be locked up indefinitely in the unlikely event that a third or more of the federation members permanently loses access to their multisig keys and the threshold required for the 11-of-15 multisig isn’t met. ## Timelock Refresh Upon peg-in, a timelock of 4,032 blocks (28 days) is set for each UTXO. To ensure that the emergency backup keys do not become active while the network is operating correctly, the timelocks are refreshed on a regular basis. There are two ways that timelocks are refreshed: 1. **Peg-outs:** When a member performs a peg-out, any change that comes back to the federation wallet is returned to an address that uses a new 2016-block timelock (14 days). 2. **Automatic:** For any timelocks that have not been refreshed through the peg-out process within 1008 blocks (7 days), the system will automatically refresh the timelock by spending the UTXO back to the federation wallet. This process provides a failsafe measure allowing seven days for the Liquid Federation to react in the event that the network stops operating. After 7 days of network inactivity, the oldest timelocks would start expiring and those UTXOs would be spendable by the emergency backup keys. After 28 days of network inactivity, all timelocks will have expired, and the entire federation wallet would be spendable. ## Emergency Backup Keys The [Liquid Network](https://glossary.blockstream.com/liquid-network/)’s emergency backup keys are held by Blockstream. The emergency backup keys also use a multisig model (but no timelocks) and are held offline in deep [cold storage](https://glossary.blockstream.com/cold-storage-security/), distributed around the world, with limited staff access. The emergency backup keys are only intended to recover the network’s funds and return the funds to the owners in the event that the network becomes inactive for an extended period. ## Upcoming [Dynamic Federations](https://glossary.blockstream.com/dynamic-federations-dynafed/) Update To reduce the Liquid Network’s reliance on Blockstream in the future, our engineering team has been working on deploying the Dynamic [Federations](https://glossary.blockstream.com/federations/) update (DynaFed) in a phased roll-out. In addition to a wide range of improvements to the Liquid Network, DynaFed will introduce the following changes to the network’s multisig model: - Expand the maximum number of multisig keys for the federation wallet (currently limited to 15). - Enable the Liquid Federation to reassign or disable the emergency keys. - Enable the Liquid Federation to lengthen the timelock parameters to extend the safety buffer. Navigation: Blockstream Help Center > Liquid Network > How does the Liquid Federation's multisig work? ## Related Articles in This Section - [How many confirmations are needed for my Liquid transaction to be secure?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/how-many-confirmations-are-needed-for-my-liquid-transaction-to-be-secure) - [What is the Liquid Network?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-the-liquid-network) - [What is the Liquid Federation?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-the-liquid-federation) - [How does Liquid Bitcoin (LBTC) work?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/how-does-liquid-bitcoin-lbtc-work) - [What is a Liquid peg-in?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-peg-in) - [What is a Liquid peg-out?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-peg-out) - [What are Liquid assets?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-are-liquid-assets) - [How does the Liquid Federation's multisig work?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/how-does-the-liquid-federations-multisig-work) (current) - [How does Liquid keep my transaction data confidential?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/how-does-liquid-keep-my-transaction-data-confidential) - [How do transaction fees on Liquid work?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/how-do-transaction-fees-on-liquid-work) - [What is the transaction capacity of Liquid?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-the-transaction-capacity-of-liquid) - [Does a Liquid address support all types of assets?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/does-a-liquid-address-support-all-types-of-assets) - [What are the different types of participants in the Liquid Network?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-are-the-different-types-of-participants-in-the-liquid-network) - [What is a Liquid Network functionary?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-network-functionary)