# What are the different types of participants in the Liquid Network? Source URL: https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-are-the-different-types-of-participants-in-the-liquid-network Updated: 2026-04-09T09:37:54.000Z Category: Liquid Network Section: FAQs --- The [Liquid Network](https://glossary.blockstream.com/liquid-network/) is an open network that anyone can freely participate in. Anyone can [set up a Liquid node](https://helpcenter.dxp-frontend.devserver.app/liquid-network/perform-advanced-liquid-operations/set-up-a-liquid-node) or [wallet](https://helpcenter.dxp-frontend.devserver.app/liquid-network/acquire-lbtc/get-a-liquid-wallet) and connect to the network, send and receive transactions, [peg in bitcoin](https://helpcenter.dxp-frontend.devserver.app/liquid-network/perform-advanced-liquid-operations/peg-in-btc-to-the-liquid-network), and issue assets. Meanwhile, members of the Liquid Federation exclusively fulfill certain key tasks that are vital to the Liquid Network’s security and operation. ## Different Types of Participants in the Liquid Network On the Bitcoin network, participants can be broadly categorized into three main groups: miners (mining full nodes), full nodes, and light wallet users. Similarly, on the Liquid Network, there are a number of different types of participants, each with varying levels of trust, security, and permissions on the network. The structure of the Liquid Network is a little more complex than that of the Bitcoin network. Participants can be categorized across two different dimensions: - **[Membership](#h%5F01EFKV6FF68GYGQPSB7JKBCPJ3):** Refers to the relationship between the participant and the Liquid Federation—specifically: have they joined the Liquid Federation, or are they a regular user? - **[Technical](#h%5F01EFKV6Q8PDF8WK94D78VY72EE):** Refers to the hardware and software used by the participant. Every participant always falls into at least one category within both dimensions. For example, a _Liquid Federation member_ running a _Liquid node_. Being a [federation member](#h%5F01EFKV8PY2H62XP44MN8E1QZ98) provides the participant with access to special hardware and software such as the [Liquid functionary](#h%5F01EFKV89KJX5KMNZMB8KEFZ9H0) and [bridge node](#h%5F01EFKV81NM03FBEK0YQ5T0W4Q3), as shown below. | | **Access to** | **Membership Status** | | | ----------------- | ----------------------------- | --------------------- | - | | **Liquid Users** | **Liquid Federation Members** | | | | **Technical** | **Light wallet** | ✓ | ✓ | | **Liquid node** | ✓ | ✓ | | | **Bridge node** | ⨉ | ✓ | | | **Functionary\*** | ⨉ | ✓ | | \*Functionary participation is currently fully subscribed but will be expanded on the launch of [Dynamic Federations](https://glossary.blockstream.com/dynamic-federations-dynafed/). ## Membership There are two types of participants on Liquid: the users that freely access the network, and the Liquid Federation members that operate the network. ### Users Liquid users include both individuals and businesses. Users can run either a [Liquid node](#h%5F01EFKVAS3P105F5TWHKW8VTYF4) or a [light wallet](#h%5F01EFKVAHW9KM5GJPATC94WQB7G). Anyone can be a user: there is no specialized hardware, and [the software required is open source](https://github.com/ElementsProject/elements) and free to download. ### Liquid Federation Members [The Liquid Federation](https://liquid.net/) comprises incorporated companies that have joined as federation members. As part of their role, members have ongoing duties to maintain and secure the network. Liquid Federation members can do everything that users can do and have the following additional permissions and responsibilities: - **PAK List Entries for Peg-Outs:** Members can add their Bitcoin wallet addresses to the [Peg-out Authorization Key (PAK)](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-peg-out) list, enabling them to complete peg-outs. - **Direct Connections with Bridge Nodes:** Members can set up bridge nodes that connect directly to Liquid functionaries via Tor. Bridge nodes can be either private or public. As a form of DoS protection, users can connect their Liquid nodes to public bridge nodes only. - **Operate a Bridge Node:** Using the direct connection, members can provide bridge node services to Liquid node users. - **Governance:** Members contribute to the decision-making process behind the development of the network, for example, voting on the [Liquid Federation board](https://liquid.net/governance) elections. - **Operate a Functionary:** Members that meet further criteria can gain access to purchase and operate Liquid functionaries, the specialized hardware that generates blocks and secures the bitcoin on the network. > **Note:** 15 of the Liquid Federation members run a functionary, which is currently the technical maximum supported by Liquid. The upcoming Dynamic [Federations](https://glossary.blockstream.com/federations/) (DynaFed) deployment will expand functionary ownership among the federation. ## Technical ![202000805_diagram_of_liquid_network_structure2048x1536px.png](https://dxp-backend.devserver.app/uploads/help-center/content/liquid-network/faqs/what-are-the-different-types-of-participants-in-the-liquid-network/900003051606.png)The distinction between technical participants is based on the hardware and software used on the Liquid Network. While some hardware and software are exclusive to the Liquid Federation, others can be freely used by anyone. | | **Light Wallet** | **Liquid Node** | **Bridge Node** | **Functionary** | | -------------------------------------- | ----------------- | --------------- | --------------- | --------------- | | **Operated by** | Users and members | Members only | | | | **Sends & receives transactions** | ✓ | ✓ | ✓ | ✓ | | **Verifies transactions** | ⨉ | ✓ | ✓ | ✓ | | **Issues assets** | ⨉ | ✓ | ✓ | ✓ | | **Initiates peg-ins (BTC to LBTC)** | ⨉ | ✓ | ✓ | ✓ | | **Connects directly to functionaries** | ⨉ | ⨉ | ✓ | ✓ | | **Initiates peg-outs (LBTC to BTC)** | ⨉ | ⨉ | ⨉ | ✓ | | **Generates blocks** | ⨉ | ⨉ | ⨉ | ✓ | | **Secures LBTC** | ⨉ | ⨉ | ⨉ | ✓ | ### Functionaries The Liquid functionaries sit at the heart of the network. A functionary is a specialized server device that includes a Hardware Security Module (HSM) for securing the functionary’s private keys. Each functionary simultaneously serves two key roles: - **Block signers:** Functionaries take turns proposing and signing blocks. - **Watchmen:** Functionaries manage and secure the BTC held on the network through the federation multisig wallet. Functionary hardware is operated by a subsection of the Liquid Federation (currently 15 of the members operate a functionary). ### Bridge Nodes Bridge nodes connect Liquid nodes to the functionaries and act as an additional layer of protection against Denial of Service (DoS) attacks. Only [Liquid Federation members](#h%5F01EFKV8PY2H62XP44MN8E1QZ98) can operate Bridge nodes. ### Liquid Nodes Liquid nodes can trustlessly validate transactions on the Liquid sidechain, [initiate peg-ins](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-peg-in), issue new assets, and send and receive transactions. They connect to the network via bridge nodes. Anyone can run a Liquid node using [Elements](https://blockstream.com/elements/). ### Light Wallets Light wallets are mobile and desktop wallets that do not download the Liquid [blockchain](https://glossary.blockstream.com/blockchain/) to verify their own transactions; instead, they rely on a trusted Liquid node. Light wallets are used to send and receive transactions on the Liquid Network only. Anyone can download and use a light wallet (e.g. [Blockstream app](https://blockstream.com/app/)). Navigation: Blockstream Help Center > Liquid Network > What are the different types of participants in the Liquid Network? ## 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) - [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) (current) - [What is a Liquid Network functionary?](https://helpcenter.dxp-frontend.devserver.app/liquid-network/faqs/what-is-a-liquid-network-functionary)