Analysis of Storage Corruption Bug
This blog post provides an update on our findings following the discovery of the storage corruption bug last week. In summary, the bug was much less severe than
This blog post provides an update on our findings following the discovery of the storage corruption bug last week. In summary, the bug was much less severe than
The Go Ethereum team is very proud to finally release Geth 1.5, which can almost be called a complete internal rewrite of the Go
The Ethereum network will be undergoing a hard fork at block number 2,675,000, which will likely occur between 15:00 and 16:00 UTC on
Testing a fork The Spurious Dragon hardfork is scheduled for the coming week; block 2675000 is likely to occur Tuesday evening (CET). The
Security Alert Affected configurations: Geth Severity: High Summary: An issue has been identified with Geth’s journaling mechanism. This caused a network fork at
This week marks the completion of our fourth hard fork, Spurious Dragon, and the subsequent state clearing process, the final steps in the two-hard-fork solution
The possibilities of zkSNARKs are impressive, you can verify the correctness of computations without having to execute them and you will not even
Vitalik suggested last week that I share my basic research and design philosophy in a blog post, I agreed but complained that it
This chapter describes the game theory and economic security modelling we were doing in the Fall of 2014. It recounts how the “bribing
With the long awaited geth 1.5 (“let there bee light”) release, Swarm made it into the official go-ethereum release as an experimental feature.