Ethereum’s Geth Client Now Processes Blocks 40% Faster, Solidity Update Launched

The newest client release for ethereum’s Geth, the main eth client written in Go, is now out with one eye-catching improvement as it “optimizes dirty object handling during block processing, leading to 40% faster blocks.”

This is just a maintenance release, so it’s a “simple” client update with no consensus changes and thus no forks or network upgrades.

The main optimization of 40% faster blocks, however, could potentially increase the network’s transaction capacity.

To clarify, this isn’t faster block production. Eth blocks remain at an average of around 15 seconds. As stated there is no consensus change.

This is instead an optimization to make the processing of blocks faster. Something of interest to mainly miners and node operators as they can now potentially synchronize faster.

But it could also have implications for the wider network because it could potentially reduce orphaned blocks (uncles), thus allowing miners to potentially increase further the gas limit (blocksize).

Whether they in fact will, remains to be seen once demand picks up above 1.4 million transactions, but that bottleneck showed ethereum clients, especially Geth, have a number of potential non-consensus optimizations that could allow for more optimal mining, and thus potentially more capacity, before Casper, sharding and so on.

The new geth release also has a new minor feature that might be of interest to dapps, called Clef, which allows you to have a “Standalone signer. It would manage you keys across multiple apps. Geth could use them, Metamask could use them, cpp-ethereum could use them,” Péter Szilágyi, an eth dev, says.

We’re sad to say the blaze it Solidity 0.420 has left the station to transform itself into solidity 0.422. The answer to life and all else is still there, 42, but the blaze it is now on boost.

The new Solidity release, as you might expect, has mainly optimizations of interest to solidity coders, ethereum’s most used smart contracts coding language.

The eye candy appears to be “return messages on errors,” so if you get told off by your smart contract you’ll know who to blame. Just as your non-coder boss will know who to blame if you don’t provide better feedback to the client.

They come in three, so our third one is sharding (uuuuuu). Well, it’s just a dev update by Prysmatic Labs, one of many teams working on sharding.

“In a sharded universe, technical updates move fast. By this I mean to say that the Sharding Phase 1 Spec that we mentioned in our last bi-weekly update is already deprecated!” So they say.

Vitalik Buterin has recommended they use a super simple base that has modifiable parameters so that they don’t have to throw out the whole thing over some “small” thing, but “kids” want to play around so what’s the harm in a little bit of “fun.”

It is almost summer after-all and they’re all busy with that #buidl thing, so we’ll let them get on with their work which you can now taste a bit if you do that coding stuff.

Source: Read Full Article

Leave a Reply