Burak is a Turkish young developer who first proposed Ark, an innovative off-chain batching transaction mechanism. There are two different implementations currently being developed, the first by Ark Labs and the second by Second. Burak has no involvement in either of these.
It was originally envisioned that Ark would require a password. This is not the case. It was initially envisioned that it would require CHECKTEMPLATEVERIFY It is necessary to build (CTV).
In order for the protocol to operate properly, it requires a central coordination server. However the Lightning Network is still able to offer the same security and functionality. Users can exit the Ark System at will as long they stay online for the time required (unless you choose to have the operator trust your funds only temporarily).
Ark, unlike Lightning does not need users to be pre-allocated with liquidity in order to get funds. Ark allows users to instantly access funds by simply logging into their wallet. No pre-allocation is required.
Explore the Ark in its various components.
Ark Tree
Virtual coins are the ones held by Ark. UTXOs (vUTXOs). This is a pre-signed transaction that guarantees the creation of a UTXO with the user’s unilateral control once it has been submitted onto the chain, but otherwise remains offchain.
The vUTXOs of each user are nestled within a tree containing pre-signed transactions or an “batch.” Ark is based on the concept of a coordinator server or Ark Service Provider, which facilitates the coordination required between users to create a new batch. When users receive funds, are onboarding or offboarding Ark, they must construct a batch and its associated transaction tree.
Trees are constructed by taking the root UTXO that is confirmed onchain and locking it with a n-of n multisig. This includes all users who hold vUTXOs within the tree, as well as the ASP. Then, the tree slowly divides into more UTXOs, until reaching leaves which represent each user’s vUTXO. The script used to guarantee each vUTXO must be signed with a 2-of-2-multisig. One key is held by the ASP and the other one by the user.
Each time the branch splits, new vUTXOs appear onchain. But there are still more internal UTXOs yet to split. The ASP and users with a vUTXO lower in the tree are all involved in the n-of n multisig that locks each of these internal UTXOs. Users begin at the vUTXO and sign all the way down to the root. The root of the tree will not be signed until each user has claimed their vUTXO. This ensures that they have access to funds in worst-case scenarios.
This will be explained in the following section. This alternate spend condition exists for both the root UTXO and every internal UTXO. It allows the ASP the ability to spend the funds all by itself.
The Connector, Transactions and Pre-Confirmation Inputs
There are two ways to conduct transactions on Ark. Each has its own security model and costs. You can choose between out-of round transfers or transactions that are pre-confirmed, as well as in-round or transactions which are actually confirmed.
It is very easy to conduct an out of round transfer. When Alice wants to send Bob money, she simply contacts the ASP to have it co-sign a vUTXO transaction. Bob receives the pre-signed transactions, along with all those that preceded it. Bob has the ability to exit the Ark unilaterally with this transaction. You can also read about how to get in touch with us.ASP must be trusted to not double-spend the money. The transactions that are not in the round can be repeated multiple times.
Users must complete an Ark transaction by engaging in the following: “batch swap.” It is not possible to confirm the transfer of a vUTXO within one batch. Users must swap an old vUTXO with a newly created vUTXO. It is possible to do this using an ASP that facilitates swaps and a “connector input.”
The ASP will take control over the vUTXO when a user finalizes an Ark transaction by batch swap. It could cause problems. What is stopping the ASP to simply keep it, and not give them a verified vUTXO for a new batch of transactions? The connector input.
The second output of the transaction is created when creating a new batch. This creates a tree made up of connector UTOs. Bob’s forfeit transaction is signed over to the ASP in order to perform the batch swap. The transaction contains one of the connector UTXOs. New batch.
It creates an absolute guarantee. Bob’s confirmed VUTXO will be in the same batch as the connector in order for Bob forfeit to work. The batch must be created before the forfeit transaction can be confirmed on chain. Bob will not be able to confirm the ASP forfeit transaction he has signed if he never receives the confirmed vUTXO.
Liquidity Dynamics in Blockspace
The ASP will provide all of the liquid funds necessary to enable transfers between users. The ASP must have sufficient liquidity in order to allow users to transfer funds between them.
Ark is built around the dynamic of liquidity. This is a major efficiency boost, because it eliminates the need for liquidity providers and ASPs to guess the users who are likely to receive large amounts of funds before the money is released. But, at the same time, the ASP has to maintain enough liquidity so that they can continue to generate new batches to users, for as long as they set the expiry period to be, until they start reclaiming their allocated liquidity.
The amount of time an ASP takes to offer new batches in order to complete pending transactions can help mitigate this to a certain extent. The liquidity requirements of an ASP who attempts to create batch in real-time as new transactions come in would be excessive. This allows an ASP to reduce their frequency of creating new batches, thereby reducing the liquidity requirement.
It also impacts blockspace. In contrast to Lightning which provides strong assurances of confirmation offchain, for Ark transactions to be as final and trustless, a fresh batch is required. You can learn more about this by clicking here. Onchain. Ark’s transaction velocity, unlike Lightning where the volume of transactions is not reflected onchain, requires an equal amount of space to be used, but in a compressed, efficient way. It creates an upper theoretical limit on how many Ark batch can be created in any time period (although Ark Trees can be larger or smaller depending on the dynamic).
Wrapping it up
Ark is in some ways almost the opposite of Lightning Network. Ark is an enormous blockspace improvement that eliminates the issue of liquidity allocation in the Lightning Network. However, it has a throughput limitation which is closely tied to the blockchain’s throughput.
It is a complementary system because of its dynamic, almost opposing trade-offs. Interoperability is also possible, so it can work with the Lightning Network. The Lightning Network allows transactions to be entered or exited by swapping vUTXOs atomically.
It is still unclear how this protocol stack will fit into the larger Bitcoin ecosystem, but there is no doubt that it has value and is likely to find a useful niche even if its original intent is not met.
“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
