.jpg)
Here’s the first Frontier patch, and it’s a big one!
Before we go any further, if your keys go back to Go 1.0 rc or C++ 0.9.36, note that you must regenerate all of your keys now. Although some versions of pre-alpha and alpha clients are secure, this depends on the code base and version. You should assume that all keys generated by these clients are insecure and vulnerable. Note that this does not affect pre-sale wallets.
Ice melting
Dissolution Withdrawal request Merged to Go client The main branch has been updated. If you are still running branch version 1.0.0, please switch to the master version.
As for C++ For users, they can also switch to master mode once merged, and binaries will be made available soon. If you prefer not to update eth but still want to help thaw the network, you can also restart eth using an additional parameter of –gas-floor 3141592.
I thought I’d also repost a quick explanation of how gas limit targeting works, and why we can’t guarantee when we’ll hit the 21k limit needed to process one basic transaction per block.
Each miner runs a copy of geth or eth. In the Frontier Genesis version, both are set to target 5k and never deviate from that number. Now, with this update, both clients will be updated to target a 3M gas per block limit instead.
But they can’t shift to the 3M gas limit this way, because the protocol forces them to slowly ascend at a certain rate. This rate is equal to the previous block limit / 1024. Now, assuming that all miners are updating their clients, and none of them messed with the settings, we will reach 3 million in 28 hours assuming a constant block time of 15 seconds including deployment. But here’s the thing – not all miners will update in a timely manner, some may forget and some may never update!
So, from now on, if the winning block is mined by an updated miner, the block limit will be adjusted upward at the intended rate, but if it is mined by a “lazy” miner who has not updated, it will be adjusted back down (since the lazy miner Still targeting 5k).
For this reason, it will take at least 6 hours to reach the gas limit of 21 thousand per block (1 trx per block), and at least 28 hours to reach 3 million. In practice, it will likely take much longer than that.
This is where the free market comes into play. Technically, miners could have colluded a few days ago to modify the client code and make the network behave differently than we thought. We only act as community advisors.
The community-adopted Genesis block is now hard-coded into clients, and you no longer need to specify the –genesis parameter to start eth or geth. However, you can still specify a handcrafted configuration block if you want to start a special thread with a different origin, for example.
Bug fixes
On the Go client side, a series of bug fixes and improvements have been incorporated into version 1.0.1, including preparing ourselves for the Go 1.5 release.
- Fixed crash in string manager #1568
- Record number fixes #1545
- Fix encryption for go 1.5 #1536
- Fix for eth_call and eth_estimateGas #1534
- Control unit Resend Repair method #1461
On the C++ client, a full external audit was performed on its keystore and encryption. We have been working on all procedures recommended by our expert reviewers. Several improvements and security improvements have been added to the client:
- A unique C++ client feature is Secure Secrets: all heap memory used to securely store your secrets is overwritten immediately upon completion
- The C++ client now relies on Boost::random_device, providing cryptographically secure random number generation
- Numerous crash and build fixes for AlethZero
- Improvements to Alethzero, especially regarding account information
- The CLI “ethkey” tool can now be used in coordination with AlethZero to inspect and sign unsigned transactions. This allows you to have a cool wallet device that is completely air-filled
Difficulty adjustment chart
Many of you have asked how the shift from Proof of Work (PoW) to Proof of Stake (PoS) will be implemented in a timely manner for Serenity. This will be addressed by the newly introduced difficulty adjustment system, which elegantly ensures a difficult split point in the next 16 months.
It works like this: Starting from block 200,000 (about 17 days from now), the difficulty will undergo a massive increase which will result in They only become noticeable in about a year. At this point (close to the cooldown release), we will see a significant increase in difficulty which will start to push the block solving time upwards.
So, after a year, the network will still be useful for about 3 to 4 months, but it will eventually reach an “ice age” of sorts: the difficulty will simply be so high that no one can find a block. This will allow us to offer Proof of Stake (PoS), possibly via KasperIf he proves himself.
