Links table
Abstract and 1. Introduction
-
Main concepts
2.1 Record attached only and 2.2 cases of the virtual device
2.3 Transactions as curry functions
2.4 The natural names of the state
2.5 Earth’s truth
2.6 Effective state representations
2.7 checkpoints
2.8 Implementation parameters: Calldata
2.9 arrangement implementation
2.10 Decision on the right situation
-
Ideal layer design 2
3.1 VM job queue and arrangement of final transactions
3.2 Provides data and collecting garbage
3.3 state final
3.4 checkpoints
-
Conclusion and references
A. Security teachers to reveal the contradiction
2.5 Earth’s truth
The basic truth of the Blockchain systems is to know what the current state is supposed to be. This does not mean, however, that we must have an effective representation of that situation, just as it is calculated – effectively, and unambiguously. We affirm that the most natural definition of the status of the Blockchain system depends on the consensus agreement on arranging all transactions since the form of Genesis (or since the case of the checkpoint, see Section 2.7).
Once the treatment parameters are registered (the final record), its implementation arrangement is determined for the previous registered transactions. Through a simple inductive intermediate, since the input condition is calculated through the final order arrangement for previous transactions, the resulting state can also be calculated from this deal, in principle. We call this “final arrangement of transactions”.
The consensus depends on the current state on the natural names of the cases, and calculating an effective representation that is not necessarily associated with this decision. Everything else is improvement.
2.6 Effective state representations
All Blockchain systems are used as a urgency record only to record the Earth’s truth. From these registry entries, the system determines the reality of consensus on one (or more) case of virtual devices. However, different Blockchains deals with a different condition.
Bitcoin only records transactions in Blockchain blocks. VM is relatively simple and the state is the number of symbols controlled by the general keys-the so-called UTXOS outputs. Registered messages determine how to transfer symbols using VM rules, but the implicit condition. In contrast, Ethereum also records a representation of the new case that is produced after all the transactions mentioned in the mass on the state of the previous mass. This condition is recorded by the “stateot” commitment, which is the root segmentation summary of the representation of the Merkle Patricia Trie of Ethereum Virtual Machine (EVM). Hyperledger [1] It takes a bitcoin-like approach and leaves the interpretation of results-the effect on VM- to customers.
Note that bitcoin miners must also have an effective representation of the state, because in order to verify new blocks, double spending examinations and etc.-only this condition does not appear on the chain. Availability is separate from always: in both cases, miners must either “catch up” by restarting transactions since a checkpoint (more about that later) or obtaining a copy of another person. Regardless of restarting transactions, there is no way for bitcoin miners to verify the condition obtained by unreliable party; On the other hand, ETHEREUM mines can easily verify the Merklized data structure (stateot).
Rollup systems use the Blockchain collection as a safety anchor to allow the implementation of “outside the chain”, where the smart contract code is performed in VM (“” Rollup “), so that many transactions can implement there with a lower (or cheaper) transaction request in the basic Blockchain. This is an attractive scaling solution, given that (supposed) calculate (supposed) on cheaper rollup, and one inherent Blockchain can support many words. Optimistic designs such as definition [8] He commits the treatment order to contract the bridge in the basic Blockchain, calculates the resulting state in Rollup, and this result is sent to the bridge contract in the basic Blockchain to verify healthy. We will discuss various health verification plans later (see Section 2.10); The main note here is that the arrangement of transactions can be determined in a separate step from the case account.
Another way to think about this is that the result of the treatment of the transaction R. It was called as soon as we have the arrangement R.. We may not have yet Calculated This case as a data structure that allows the search for the value of the keys efficiently, but there is no doubt about what this situation will be-all of the matter, given that its name will reach the same abstract maps, even if its concrete representation-the difference in the actual options for data structures. Bitcoin only calls the current state.[3] Systems that resemble ETHEREUM name and a specific representative of the state. Some of the naming operations separate the name from the case account, where the treatment order is obligated to the 1 Blockchain first, and the proper resulting condition is calculated outside the chain, in layer 2, and the commitment to layer 1 at a later time. Other Rollups uses the Mempool design for rollup, so that the arrangement of transactions is determined by the Rollup contract instead of the basic Blockchain, and this arrangement is committed along with the fragmentation of the calculated state. This design reduces the number of transactions in the basic Blockchain, and trades the cost of processing low transactions there for the narrow conjugation between the finals of arranging transactions and state identification.
The separation of fears should be explicit. The consensus layer is responsible for making a non -changing record, only. The primary purpose is to register the treatment – in order to be implemented. This calls the resulting state, and everything else is secondary. Computing and agreement on this situation can come later, as a promised value. The result can be recorded – correspondence between the name called the name and the representation of the state – the same to make the sharing of the state representation easier. This means: Bitcoin records only implementation; ETHEREUM records are both the arrangement of implementation and an effective representation of the resulting state in a tightly associated manner; On the other hand, the separate layer Rollup designs, but separately, do not invalidate problems related to the validity of the calculated condition necessarily arrange the committed transaction.
Note that it is important to calculate the situation and reach a consensus on it, because Blockchains are not closed systems: the main transfers between Rollup and Blockchain are an example of external procedures that depend on the situation; In general, it requires any contracts that can cause effects outside the chain, such as charging the goods, unanimously and the value of the state.
From our point of view, getting an equivalent but more efficient representation of a specific situation is an important improvement. In fact, the commission of the implementation of transactions leads to one feeling in the end – the finals of progress, which allows us to name a committed state. The reckoning of the sixties and reaching the agreement on the result gives a secondary sense of the final – “the finals of the state’s value”, which allows us to trust Use The value or representation of the state.
Authors:
(1) Bennett Yi, Oasis Laboratory;
(2) Al -Fajr song, Oasis Laboratory;
(3) Patrick McCuri, Ingoura;
(4) Chris Backland, Ingoura.
[3] Although countries are realized periodically, when Inspection points It is created. See section 2.7 for more details.
