以太坊开发者会议回顾：坎昆升级、硬分叉与布拉格

Author's research vice president compiles the value of carbon chain in Qin Jin. The developers of Ethereum gather for a conference call, which is usually presided over by the head of the Ethereum Foundation agreement. It is a biweekly series of meetings for developers to discuss and coordinate the changes in the implementation layer of Ethereum. This week's meeting was presided over by an anonymous developer with the net name. The developers reconfirmed the activation dates of the next three public test networks in the upgrade, and they also discussed the priorities of code changes in the next hard fork upgrade. The client team has been preparing a new version for the test network since the last conference call on January, and the developer asked the client team to provide the latest progress of cutting the new version because of the delay in the upgrade test. The developer confirmed that the team will prepare the new version of the hard fork next week, but the version targeted will be a pre-release version, which means that it will not be the version recommended for use on the main network of Ethereum. After the hard fork, the team plans to release another version. One version, which contains some changes and updates, recommends users to run on the main network and test on or on the test network. Although it indicates that the team is satisfied with the hard fork activation date as discussed above, he suggests that the hard fork activation date should be determined after the hard fork. Since then, the person in charge of the agreement support of the Ethereum Foundation has proposed the fork activation time of the public test network for these three Ethereum public test networks. The fork activation time is as follows: Year, Month, Era, Time Stamp, Year, Month, and Year. Meta-timestamps Year Month Era timestamps Ask other client teams whether they agree with the proposed hard fork activation time. All the client teams attending the conference call, including and, confirm that they think the timing is good and they can release the version for the node operator at the latest next week. The client team points out that since they are still testing some network functions of their clients, their released version may be different from the pre-release version timeline, and then discuss with the suggested activation time of the test network. The developer with the pseudonym suggested that the update date of the last two test networks before the main network should be postponed. We should try not to promise the date now, because it is a problem to add a new version with the correct era without making any changes. It is a problem to delete a version and fix the error, which is much longer than a few weeks. It means that the client team does not need to release a new version until a week after the hard fork, so unless it is on or. Later, I found an upgrade problem on the internet, otherwise I don't have to delete the new version. The developer said that he thought it would be harmless to set a date for the test network, because if there is a problem on the internet, the developer can change the date at any time. barnabas Bussa, an engineer of the Ethereum Foundation, wrote in the chat room that in his opinion, it is only necessary to release a new version for the upgrade of the network. A developer named agrees with this view. He said that the developer can set a tentative date for the hard fork. However, it is suggested that we should look at the progress before June, and add a week of testing time between the client and the hard fork activation, which basically takes two weeks to analyze instead of three weeks. He said that adding a week of testing time can let the client release soak for a few days before the client team needs to cut the new version again for the next test network upgrade. This is the problem I want to point out, adding that if the client release is fully analyzed and tested, it will be hard fork activation. The idea that there may not be a three-week turnaround time between activities has aroused controversy. Ansgardi Trixis of the Ethereum Foundation said that the time between the activation of the first upgraded public test network and the activation of the upgraded main network is usually the developer's deadline, and there is no need to extend it. However, he also pointed out that the developer should discuss the desire to extend the interval between test network upgrades more seriously in the context of hard fork, rather than just upgrading, saying that if someone wants to have a longer process, then we should have it. I agree that if we discuss this issue as early as January, developers will probably be more tolerant of the extended test network schedule. I think part of the reason is that we want to complete the upgrade last fall, so now we are really trying to achieve this goal. I think our schedule should be more active and adhere to a positive schedule. According to the views shared by developers on the conference call, engineers of the Ethereum Foundation. It is suggested that the upgrade of hard fork should be postponed for about a week and the date of hard fork should be set at the conference call after the upgrade. He said that what I really want to avoid is that we have to call again to confirm the date. He added that I hate calling again just to say that we can start now, but now we have to wait for two weeks before we can really start to realize it. In order to calm the emotions of all parties, the developer suggested that it be hard fork. Create two sets of tentative dates. If the result of hard fork is positive, the developer can stick to one set of dates. If the result of hard fork is negative, the developer can use the other set of dates. However, both of them are opposed to this idea, because before the developer sets a new timetable for hard fork, it is necessary to evaluate the nature of the errors and problems on the Internet. By the way, a pseudonym developer of the test team of Ethereum Foundation asked the developer if he wanted to wait until the evaluation was completed. Upgrading after expiration refers to deleting data from the Ethereum state after about two weeks. Both the source and the team are in favor of evaluating the expiration on one of the three test networks before the main network is activated. It is emphasized that waiting for expiration on the test network will also help the second-layer protocol team and application developers to prepare for the upgrade. Although it is not necessary to observe the expiration on the Internet, it may be a reason for extending and intervening the test period. On the other hand, the second-tier team can ask the developer if he is willing to stick to the proposed timetable, that is, the month, day and the month after the upgrade one week. Because the developer has no more different opinions, he said in the chat that he hopes to upgrade and test the network at the same time on the month and the day instead of upgrading the former one week in advance. The test network timetable reconfirmed in the message after the call remains unchanged for the time being. What should be given priority for the next upgrade after the developer discusses? 比特币今日价格行情网_okx交易所app_永续合约_比特币怎么买卖交易_虚拟币交易所平台

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

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