Vitalik最新文章：以太坊Purge阶段需要清除哪些东西

One of the less well-known hard bifurcations of Shanouba Bitcoin Trading Network recently is that it deletes most of the functions of operation code, which is a key example of the often underestimated part in the development of Ethereum protocol. This is an important part of what I call the efforts to simplify the protocol by eliminating complexity and adding new security guarantees. The project of streamlining Ethereum and clearing technical debts will have more similar spirit, so it is worth knowing how to achieve it. The standard and what other things may be removed in the future how to simplify the Ethereum protocol reduces the function of the operation code. It will destroy the contract calling it and empty its code and storage, so it will only be effective when the contract is created during the same transaction. This in itself does not reduce the complexity of the specification. However, it does improve the number of memory slots that can be edited in a single block by introducing two new invariants. The maximum number is roughly if the contract has a non-empty code at the beginning of the transaction or block. At the end of the transaction or block, it will have the same code. Before that, these invariants were not contracts with a large number of storage slots. An infinite number of storage slots can be cleared in a single block, which will make the implementation of the tree more difficult and make the implementation of the Ethereum client more complicated because they need extra code to effectively deal with this special situation. In fact, the contract can even be recreated with different codes immediately after that. It is more difficult to use the code base to verify the transaction in the abstract wallet of the account, and it is not easy to be attacked. Now these invariants make it easier to build Ethereum clients and other types of infrastructure. In a few years, I hope that the future can complete this work and completely eliminate what others are doing. Recently, thousands of lines of code have been deleted, and the support for the network has been deleted. This officially reflects the fact that we no longer need code to worry about empty accounts. Please refer to it and introduce this concept as. The storage window in the part of Shanghai attack repair is days, which means that Ethereum nodes only need about to store data, and this number will not increase with the passage of time. The first two have significantly improved the experience of client developers, and the latter has significantly improved the life of node operators. What other things may be needed? Precompiling precompiled is an Ethereum contract, which has no code but logic that must be directly implemented by the client itself. This idea is that precompiling can be used to achieve the goal that cannot be realized in. Nowadays, the use of precompilation is very successful, especially the application based on elliptic curve precompilation. However, there are other precompilations that are rarely used. Hash function is introduced to support better compatibility with Bitcoin, and the precompilation that returns the same output as its input is introduced to support better compatibility. It is proved that the demand for these precompilations is far lower than expected. It is widely used because it is the simplest way to copy data, but the operation code has replaced it since then. Unfortunately, these precompilations are a huge source of consensus errors and a great source of pain for new implementations, including the friendly implementation of circuit form verification. There are two ways to delete these precompilations, just delete them, for example, which is simple, but it will destroy any application that is still using it and replace them with code blocks that perform the same operation, although it will inevitably For example, this draft is done for identity precompilation, which is more difficult, but it will almost certainly not destroy the application that uses it, unless in rare cases, the cost of new code exceeds some input blocks, historical blocks, and now every Ethereum node is expected to permanently store all historical blocks. People have long thought that this is a very wasteful method and it is unnecessary to run Ethereum nodes because of high storage requirements. We have introduced it and only need to store it for about days. After using it for a period of time, the Ethereum block will also be deleted from the default Ethereum node. A key problem to be solved is that if the old historical record is not stored by each node, what should be used to store it? In fact, large entities such as block browsers will do so. However, it is also possible and not difficult to make the protocol to store and transmit this information. This is more optimized for the task. The Ethereum block chain is permanent, but it requires every node to be forever. Storing all data is a very overkill way to achieve this permanence. One method is a simple peer-to-peer network with an old history, and the other is a protocol that is more clearly optimized for the use of Ethereum, such as portal network or meme format. Reducing the storage required to run Ethereum nodes can greatly increase the number of people who are willing to be nodes and reduce the synchronization time of nodes, which also simplifies the workflow of many node operators, so it can greatly improve the access of Ethereum nodes. Centralization Potentially, if each node stores a small number of historical records by default, we can even store roughly the same number of copies of each specific historical record on the network as we do today. The reform of direct reference to this draft log was originally introduced to enable applications to record information about events on the chain so that decentralized applications can easily query this information. Using filters, we will be able to quickly browse the historical records and identify several logs related to their applications. Block and then quickly identify which single transaction has the required log. In fact, this mechanism is too slow. Almost all access history records are ultimately not through calls to Ethereum nodes or even remote managed nodes, but through centralized additional protocol services. What can we do? We can delete filters and simplify opcodes so that all it does is create a value that puts the hash value into the state, and then we can build a separate protocol usage and incremental verifiable calculation to generate verifiability. Knowing the correct log tree, which represents the easy-to-search table of all the logs given and the decentralization of the logs and the desired applications, can be turned by using these separate protocols. Today, most of the block structures of Ethereum, including transactions and receipts, are still stored in outdated formats based on sum trees, which makes it unnecessary to develop applications using this data. The consensus layer of Ethereum has turned to cleaner and more efficient data sources, but we still need to complete the conversion and move the execution layer to the same structure. The main advantages include simpler and clearer specifications. Compared with the current sextuples, most situations. 比特币今日价格行情网_okx交易所app_永续合约_比特币怎么买卖交易_虚拟币交易所平台

注册有任何问题请添加 微信：MVIP619 拉你进入群

文章转载注明 网址：https://netpsp.com/?id=55503