Original author: DaPangDun
In the early days of research on the BTC ecosystem, I looked at the sidechain network, and at that time, based on the judgment of “insufficient originality”, there was no detailed research, focusing on the research of the RGB protocol. A few days ago, the project team of pprgb and I discussed whether there is a possibility of “mapping” the distribution on Liquid, and then the research found that there is a “bridge” code between the RGB protocol and Liquid, although I have not tested it, but I found that the code has been there for a long time, indicating that it has been on the roadmap for a long time. Therefore, I began to study Liquid, and gradually understand its principles, technical characteristics, ecological status, etc., before I came to this article.
This article can only be used as a “shallow talk”, because Liquid came out very early, belongs to the category of “ancient protocol”, I don’t have much time to research, and there must be a gap with the understanding of OG under this protocol, so this article is only recorded as a “study note”.
Liquid is a BTC layer-2 settlement network based on the idea of sidechains, which aims to connect cryptocurrency exchanges and institutions more effectively, enabling faster and more confidential BTC transactions and the issuance of digital currency assets.
In the early BTC scaling controversy, two ideas emerged: one was the big block (if the TPS was not enough to make the block bigger), and the other was to make various attempts outside the BTC to anchor or hook up to the original chain in some way, and the sidechain was one of them.
A sidechain is a mechanism by which tokens from the original blockchain (in this case, the BTC of the BTC main chain) are securely used on a separate blockchain (in this case, Liquid), with new rules, performance requirements, and security mechanisms.
In this way, when it is necessary to do some new function tests with security risks in the original chain, or test new functions that cannot be implemented in the original chain, it can be carried out in the sidechain.
Of course, in order to ensure the anchoring of the original chain and the sidechain, there will be a two-way peg mechanism to anchor the main token.
Liquid is one of the BTC’s sidechains that allows users of the Liquid network to move BTC between the two networks through a two-way peg. The BTC used in the Liquid network are known as L-BTC, and each L-BTC is backed by a verifiable equivalent number of BTC, guaranteed by Liquid members known as Functionary.
The figure above shows the process of the main chain BTC entering the side chain through Peg-in and converting it into L-BTC, and then transferring from the sidechain to the main chain through Peg-out, and the intermediate process is guaranteed by Functionary.
Compared to traditional BTC trading, Liquid offers a lot of features
The BTC transferred to the Liquid sidechain can be settled within 2 minutes, which is much shorter than the main chain transfer
The block time of Liquid Network is one minute, which greatly improves the transaction confirmation speed compared to the BTC main chain
3.2.1 Concept of Confidential Transactions
The default transaction on Liquid is a “confidential transaction” that hides the amount and type of assets traded, keeping the user’s financial data safe.
This privacy enhancement was proposed by Adam Back in 2013 and later formalized by Gregory Maxwell, Andrew Poelstra, Adam Back, Mark Friedenbach, and Pieter Wuille.
Confidential transactions on Liquid allow either two parties to trade, while no one else can see the assets (e.g., L-BTC, L-USDt) and the amount of the transaction (even Liquid Alliance members and staff can’t see this information). This kind of privacy can avoid the tracking of large transactions by on-chain analysis software, which can expose one’s own transaction intentions.
Of course, because the assets on Liquid fall within the scope of regulatory requirements, including basic service providers, etc., these may be required for KYC; Some projects may require KYC when Peg-out to the main chain due to regulatory or anti-money laundering measures. However, for most people, the vast majority of operations are optionally confidential.
3.2.2 Blinded and unblinded data
Technically, Liquid refers to “the process by which the number and type of transferred assets are cryptographically hidden from everyone as ‘blinding’”, and only the recipient can decrypt the amount sent in the transaction.
Of course, the receiver can choose to share the private blinded key of a particular transaction with any third party he trusts so that party can verify the amount and the type of asset.
So, in Liquid’s trading, in the explorer of some products, we see the difference between “blinded data” and “unblinded data”.
The above figure is the “blind data” of a transaction, we can only see that there are inputs and outputs, but we can’t see the specific assets and amounts, which is also the data status that others see
The picture above is the display of the blind data after the “non-blind”, here I can only see my own input and output, the input is three L-BTC, the output is to get 9 PPRGB, and there is an L-BTC return; For the counterparty, his “unblinded data” is the remaining confidential part
Liquid allows individuals, institutions, project parties, companies, etc. to issue a variety of digital assets, including: tokenized fiat currency, tokenized non-BTC cryptocurrency, digital collectibles, reward points, and certified assets.
3.3.1 Asset Registry
Assets that have been issued in Liquid are given a unique identifier (64 hexadecimal characters) when they are created. This is the unique identifying information of the issued assets that are clearly recorded on the Liquid blockchain. Any additional human-readable metadata that can simplify the identification of issued assets at the UI level, can be submitted during issuance, and published on a server such as the Asset Registry. Metadata that can be linked to an asset contains:
Assets issued on Liquid can be “re-issued” or “burned”, which can be understood as the concept of asset contract upgrade in “RGB”, which usually needs to be set up and confirmed through the “m of n” multi-signature scheme
3.3.2 Stablecoin (tokenized issuance)
In this case:
Fiat currency is deposited into a bank account and held in escrow by the issuer
The issuer generates tokens in Liquid that represent the amount in the account and distributes the tokens to the depositors of the account
If the owner of one of these tokens wishes to receive fiat currency in return, he can redeem it through the issuer. The issuer can then burn the tokens and maintain an equal supply of fiat currency and outstanding tokens
The issuer can certify to any auditor or regulator that the number of outstanding tokens always corresponds to the bank account balance
Issuers also have the option to use Liquid’s scripting capabilities to comply with different regulations around the world without adding any human requirements to staff.
USDt
Tether’s stablecoin has been issued on the Liquid network, and as a stablecoin, it participates in various exchanges of Liquid’s ecological protocol, and we can see the situation of the stablecoin through Mempool.
L-BTC and stablecoins can currently be withdrawn directly to the Liquid protocol via Bitfinex.
3.3.3 Tokenizing other currencies (financial currencies or cryptocurrencies)
For example:
Blockstream Mining Note and El Salvador Bitcoin Bond
Various tokens on SideSwap
Liquid members can create tokens that represent staked cryptocurrencies. These tokens can now be traded and settled between Liquid users with the same speed and privacy as BTC and other issued assets. This approach also allows exchanges and traders to safely handle these assets without having to support the underlying asset. This opt-in model allows users who wish to benefit to work with parties they trust to issue and secure an asset without requiring the entire alliance to know about the asset.
For exchanges, using Liquid can provide their users with the ability to deposit and withdraw funds quickly and privately. The implementation logic is as follows:
The exchange will hold a portion of the funds on the Liquid network
When a user wishes to make a deposit on an exchange, they will request the exchange to generate a Liquid deposit address on their behalf
The client then takes the address to another exchange and requests to withdraw Liquid
The sending exchange will deduct the client’s balance and send the funds via Liquid to the receiving exchange. When a transaction receives two confirmations, the receiving exchange can deposit funds into the user’s account without the risk of double spending
The entire process is usually completed in less than three minutes after the original transaction is sent
This mechanism is mainly for institutional traders or arbitrage traders, and it allows institutional funds to be quickly transferred to any exchange that supports Liquid deposits, realizing trading opportunities. And it will transfer the custody risk of institutional funds from a single exchange to the entire Liquid Alliance.
Liquid is governed by its federation of members, the Liquid Federation, which includes major exchanges, trading desks, wallet providers, payment processing services, financial institutions, and other significant companies in the Bitcoin space, which are geographically and geopolitically dispersed around the world. Each member does not have a single control, and they ensure network security through multi-signature smart contract collaboration.
For Liquid users, there is always the ability to self-verify activity on the network with a Liquid full node.
The diagram below shows the governance structure and the responsibilities of each part
The parent developer of the Liquid Network is: blockstream
Founded in 2014, Blockstream has been a leading provider of blockchain technology with a mission to build crypto financial infrastructure on top of the most powerful and secure blockchain, the BTC.
The CEO of the company is: Dr Adam Back
Blockstream is a diversified company that has gone through multiple rounds of heavyweight funding, and its products cover many different aspects
From the perspective of the development process, the rhythm is very good, and it is not bad for money, multi-line advancement, and orderly
The ecological infrastructure projects on Liquid are very complete, including wallets (custodial, non-custodial, plug-ins, mobile, desktop), NFT marketplaces, trading platforms, lending platforms, asset issuance platforms, compilers and other related auxiliary tools.
On the whole, the ecological projects on Liquid are very complete, the protocol itself has been continuously developing, the docking formal exchanges and institutions are also expanding, and the financing amount is also very dazzling.
The overall product architecture and development process show an obvious regular army rhythm, multi-line advancement, and step by step expansion.
However, judging from the prosperity and transaction frequency on the sidechain, the frequency of use is very low, and I guess it is because it is positioned in professional institutions and companies, so that ordinary retail investors have little participation. If there are few people researching, then the relevant tutorials will be less popular, resulting in a simple account that many people may not be able to figure out.
As the BTC ecosystem develops into one of the main narratives of this round, I think this kind of sidechain protocol will enter the field of vision of ordinary retail investors; Perhaps officials can think about some marketing behaviors (although they may not care about these for companies at this level) to facilitate the participation process of ordinary users.
Although the implementation paths of the two are very different, there are many similarities, such as:
** 2) The implementation is functionally similar. ** can improve the speed of network transactions and confirmations, can issue multiple types of assets, can deploy smart contracts, can be connected with the Lightning Network, and are designed to develop in the direction of compliant assets.
** 3) does not destroy the original chain. ** Many foreign BTC old OG tend to maintain the “cleanness” of the BTC main chain, and all the expansion is carried out as much as possible without destroying the characteristics of the original chain, whether it is a side chain or off-chain verification, it will not interfere with the operation of the original chain, in principle, I agree with this concept.
RGB In the core code, there is already a bridge code with Liquid, maybe in the future we can see “Liquid+RGB”
Liquid’s official website
Blockstream’s official website
Liquid network whitepaper
Liquid Developer Documentation
Link to original article