Introduction to Liquid for developers

If you are going to work on software using Liquid, the sidechain of Bitcoin, there are several concepts you need to be familiar with. This article aims at developers and is based on a presentation I held for the Pixelmatic team.

Disclaimer: this is an introduction and it does not cover everything obviously. And I simplified some explanations on purpose.

As a prerequisite, if you are not familiar with Bitcoin, you should read my introduction to Bitcoin here:

Special thanks to Sosthene for proofreading my article and his feedback! Follow him on Twitter.

Let's start now! And to discuss Liquid, we need to discuss first: Elements.

What is Elements?


It is a fork of Bitcoin extended to be a sidechain platform with these features:

  • Confidential Transactions
  • Issued Assets
  • Federated 2-Way Pegs
  • Signed Blocks
  • Additional opcodes


OK, whatever, but what’s Liquid?


  • Well Liquid is an instance of Elements. Set as a sidechain of Bitcoin and maintained by Blockstream.
  • It is managed by a static federation of 15 members, but soon dynamic.
  • It is configured to have a block time of 1 minute.
  • And its main currency is L-BTC (Liquid Bitcoin), the result of the pegging of Bitcoin.

More details:

What are the features of Liquid?

Let’s see a bit more details on the different features of Liquid/Elements.

2-way pegging of Bitcoin



Pegging in BTC from the Bitcoin mainnet into the Liquid sidechain consists of depositing BTC into the Liquid Bitcoin wallet that is managed by the Federation. 102 confirmations on the Bitcoin mainnet are then required for you to claim your amount of L-BTC due, and the functionaries then grant you the corresponding amount on the Liquid sidechain.


Pegging out BTC from the Liquid sidechain back into the Bitcoin mainnet consists of receiving the BTC from an anonymous functionary from his wallet after being granted the amount by the federation.
2 confirmations on Liquid are required for the operation to be allowed. Then the Federation will co-sign a transaction out of their 11 of 15 multisig wallet that is sending out the amount requested to one of the functionaries described anonymously. Finally, the functionary processes the transaction that will grant the BTC to the requester of the peg-out.

🙈 Confidential Transactions

  • Amounts and assets are blinded using a blinding key, but UTXOs are visible
  • There is a master blinding key that is generated from the wallet seed and derived as needed for each address:
    blinding_private_key := HMAC_SHA256(key=master_blinding_key, msg=script_pubkey)
    where script_pubkey corresponds to a specific non-confidential public address you want to make confidential
  • That means that a Liquid wallet consists of two things: an extended private key and a master blinding key.
  • Also, every confidential address is a non-confidential address blinded using the master blinding key. So the confidentiality is essentially a layer built on the top of classical HD wallets.
  • Note that you can dump a specific blinding key to allow a tier to unblind it using the RPC unblindrawtransaction. And once in possession of the blinding key, any transaction happening with that specific address will be visible to the tier.

    FYI Blockstream Green has a feature to open esplora with the blinding keys to allow a tier to see a confidential transaction unblinded on the web.


White Paper: Blockstream

Specifications: Satoshi Labs

💰 Issued Assets


  • One asset on Liquid/Elements has these attributes (all saved in the blockchain):
    • An asset ID (generated by Liquid)
    • A total supply
    • An optional reissuance key
    • An optional contract hash
  • Reissuance keys are also an asset that comes with at least a total supply of 1 sat
  • L-BTC is also an asset, a special one that can be pegged in and out: Details
  • The bare minimum to issue an asset:

    elements-cli issueasset 0.00000100 0

    -> It issues a confidential asset with a total supply of 100 satoshis and no reissuance key.

  • The contract defines metadata about the asset like its name, ticker, domain owner, precision, etc. Example the EXOeu token:

    "entity": {
    "domain": ""
    "issuer_pubkey": "030cff26f9c0d365f090e24917277e23269d7ef5d7f06dec9f09de9255b8950208",
    "name": "EXO Token Europe",
    "precision": 0,
    "ticker": "EXOeu",
    "version": 0


  • To be able to reissue, you need only one token (satoshi) of the reissuance asset.
  • If you have issued more than one reissuance asset, it means you can share that asset to others person. Then everybody who has one can reissue the asset. Though be cautious with that use-case because reissuance can be confidential, then it's nearly impossible to verify how much of the asset is in circulation.


  • By default, assets are not registered on the Liquid Asset Registry.
  • That gives you a chance to reissue another asset if you made a mistake before registering it.
  • But once registered, it is irreversible and the tuple domain + ticker will be occupied forever.
  • Details of the asset registration:

🪢 Federation


  • The federation is composed of 15 functionaries
  • They can propose blocks to be added to the blockchain in a round-robin fashion
  • They co-sign blocks, a block needs 11 of 15 signatures to be valid
  • They process peg-outs.
  • When the federation will become dynamic, the total number of functionaries may vary dynamically

📃 Liquid RPC interface

Being a fork of Bitcoin, we find the same RPCs as its parent, plus some new ones like issueasset, blindrawtransaction, and more:


🧰 The Liquid Ecosystem

For Users

White paper

Compatible Wallets

Centralized Exchanges



For Developers



Cached API/Backend



Wallet Tools

Environment stack

Sidechain available environment

Alike Bitcoin, Liquid has multiple environments at your disposal.

You can set up in your elements.conf the chain you want to use.

Liquid Regtest (chain=liquidregtest)

  • I am lying to you, actually. You can input any not known chain, and it will create an Elements environment, with the parameters of your choices. So liquidregtest is not a known chain, it will start a chain named with this name. But you could name it differently like andrewschain, ethereum, or whatever. Details:
  • Regtest stands for regression test mode. It's a mode you use to do local development.
  • When initializing your node, you can specify the number of free coins you will create and that will serve as your main currency (your own test Bitcoins).
  • There are no pegging, mining, or federations in place. But you can generate blocks on demand.
  • To simulate a production environment, you can set up a cron task to generate a block every minute.
  • Everything you do stays local in your node.

Liquid Testnet (chain=liquidtestnet)

Liquid Mainnet (chain=liquidv1)

  • The production environment of Liquid.
  • As mentioned before, the block time is 1 minute, and mainnet Bitcoin can be pegged in and out of it.

🎇 Conclusion

With this knowledge, you should have enough to get started to work on Liquid.

To sum up, here are my advice, if you are willing to:

  • add payment in L-BTC or another Liquid asset on your e-commerce website, look at BTCPay and WooCommerce with the Liquid+ plugin:
  • create a Liquid wallet, you can either look at the LDK made in TypeScript so good for web apps, or GDK made in C/C++ good for desktop or native apps but also has wrappers for Java, Python, and Swift,
  • issue an asset (either NFT or fungible tokens too), you can look at either Blockstream AMP or build a custom solution with liquidjs or go-elements
  • create an NFT trading platform, you can fork off Raretoshi
  • create a SWAP/DEFI platform, look at coinos open source projects:

And to go to deeper in the rabbit hole, you can start searching on these subjects:

  • Multisignature wallets
  • Taproot
  • Partially signed transactions
  • Atomic swap

Have fun!

Did you find this article valuable?

Support Sonny Alves Dias by becoming a sponsor. Any amount is appreciated!