Recently, rollups has become the focus for scaling Bitcoin. It is the first thing that truly scales bitcoin. “steal the limelight” The Lightning Network has a wider reach in terms of mindshare. Rollups aims to be a layer two off-chain that isn’t bound by or restricted by the limitations of liquidity that are at the core of the Lightning Network. End users needed someone to allocate (or “lend”They can either send them money in advance to enable the receiver to get the funds, or they can use intermediary routing nodes that require channel balances to facilitate the transfer of payment amounts from the sender to the recipient.
The original intention was to develop these systems for Ethereum, and other Turing Complete systems. But in the last few years there has been a shift to porting them onto UTXO based Blockchains like Bitcoin. In this article, we will not be discussing the state of Bitcoin at the moment, but rather the functionality of a idealized rollup, which people aim for long-term, depending on features Bitcoin doesn’t currently support. Specifically, the ability of Bitcoin to verify Zero Knowledge Proofs directly.
A rollup is built around a simple architecture: a single user account, or in Bitcoins’ case a UTXO (Unified Transactions Object), contains the current balances for all the users. A merkle-root of a merkle-tree is included in this UTXO, which commits the balance of all existing accounts within the rollup. To propose a spend off-chain, a user still needs to sign something using a public/private pair. Users can leave the rollup at will by simply creating a transaction to prove their account’s membership in the merkle trees.
In order to finalize off-chain transaction, the operator must add a ZKP for transactions which update the account balances merkle roots on-chain. If this ZKP is not included, then the transaction would be invalid. This proof enables people to verify all off-chain account changes were approved by the respective account holders, and that operator did not conduct a malicious update to balances in order to steal from users or redistribute it dishonestly to other users.
How can users get their branches in the tree to allow them to exit without permission?
Proper Rollups
A proper rollup will put the data directly onto the blockchain whenever a new transaction is confirmed off-chain or the account status changes. The entire tree would be ridiculous, so only the necessary information to reconstruct it is stored in the blockchain. If you were to implement a naive solution, all the existing account balances in the rollup could be added by the update transaction.
Balance diffs are used for more complex implementations. It is basically a list of all the accounts that have been updated. The rollup updates can then only be used to include those accounts that have had money added or subtracted. Changes to the way you think Users can then scan the chain to see any changes in account balances. The user can scan through the entire chain. “do the math” The merkle tree is constructed by retracing the balances from the start of the account roll-up.
It saves on overhead, blockspace and money while still giving users access to information they need to leave unilaterally. This data must be made available in a rollup that is formal and uses blockchain technology. A transaction which does not contain the account summary and account diff will be considered invalid.
Validiums
This is a way of addressing the availability issue for data that users can withdraw. The rollup must still enforce the fact that data is available elsewhere. Other blockchains have been used in the past for similar purposes, and are specifically created to act as layers of data accessibility for rollups.
It is a paradox that security can be as robust. Consensus rules ensure that data posted to the Bitcoin Blockchain is accurate. When it’s posted on an external system it will only be able to verify the SPV that it was uploaded to the other system.
The oracle is the problem that arises when attempting to confirm data in other chains. Bitcoin’s blockchain can verify only what is on the blockchain. The best way to get in touch with us is by calling (08) 987-0909. It can only verify ZKPs. It cannot, however, verify whether a block that contains rollup data has been publicly broadcasted after its production. This cannot be used to verify whether external data are actually available publicly.
The data can be withheld by creating a false commitment that the data will be published. This is done to move the rolling up forward, however, it is never actually released. The users’ funds are no longer available for withdrawal. Only a system completely separate from Bitcoin that is based on value and incentives can provide a real solution.
Rock and Hard Place
It creates a quandary in the context of rollups. In terms of data availability, the choice is binary: either post the data on the Bitcoin blockchain. This decision has huge implications on both rollup sovereignty and security as well as scalability.
Use of the Bitcoin blockchain as the data accessibility layer places a ceiling on rollups’ ability to scale. The blockspace is limited, so there are limits to how many rollups and transactions can be processed by all the rollups combined. off-chain. Every update rollup requires blockspace that is proportional to how many account balances have been changed since the last upgrade. Data can only be compressed to a certain extent, according to information theory. After that there are no further scaling benefits.
In contrast, by using another layer to provide data, the hard limit on scaling gains is removed, however, it introduces new issues of security and sovereignty. The state of a rollup utilizing Bitcoin as the source for data is not changeable without users’ data. Validiums’ guarantee is entirely dependent on how well the external system can resist data and gaming.
Block producers on the external data accessibility system can now hold Bitcoin rollup user funds in hostage. They do this by creating a block but not broadcasting the block to make data available.
What will we be able to do if Bitcoin ever gets a perfect rollup implementation that allows users unilateral withdrawals? Which is worse, the rock or the hard place if we ever do get to an ideal rollup implementation on Bitcoin that actually enables unilateral user withdrawal?
“This article is not financial advice.”
“Always do your own research before making any type of investment.”
“ItsDailyCrypto is not responsible for any activities you perform outside ItsDailyCrypto.”
Source: bitcoinmagazine.com
