sub 0.01 incoming after fork? KEK
Some people want the price to be lower than 0.01 so that they can buy more. It could be the motive of the trolls.
The Ethereum price is still over the 0.018 range. It seems most of the people think the hard fork is a success.
The price of Ethereum is still around 0.02 at the moment, that is after the revival of the Ethereum Classic.
That is quite interesting. Even today, the Ethereum price is still over 0.019. Not many people are dumping.
The Ethereum price dropped to 0.013 and rose to 0.018 again. It seems there are still supporters for it.
The bitcoin price is still over 0.019 at present. So it is quite resilient. The Ethereum trolls might be disappointed.
That is right. The combined value of the ETH and ETC is almost the same as two weeks ago. The Ethereum is doing very well.
How you sure that ethereum is doing well . i think its because of value right now the price right now is really high and its not a good to invest right now in bitcoin unless if the price will getting low again and buy when the price crash again.. ethereum is alive again according to other traders many whales here are saying that ethereum is scam or hack or dont invest so that they can buy low price of ethereum after the price is increase again traders will be attract to invest again so that the price will increasing whales will sell again and repeat the procedure.
If the price of Ethereum does not drop below $5, I think it is doing well. As most people predict it would be $1 now.
I do not see the Etheruem price will drop too low. It is still being developed activeluy by the Ethereum Foundation.
Time will tell, because to me it seem Ethereum is losing their initial charm, the integration of Segregated withness on Bitcoin is going to really affect the platform unless you want to put cost ahead of security
There is still active development of the Etheruem. So there is no worry.
Code Coverage for Solidity
Ensuring the security of deployed Ethereum contracts is one of the most important challenges facing Ethereum developers today. After the unfortunate problems with the DAO, the resulting hard fork and associated community fallout, hopefully no-one reading this article would disagree. Indeed, there was a whole session devoted to the topic at the recent DevCon2, with talks spanning formal verification, coding best practices and more. However, the Ethereum community seems to have been silent regarding one of the first tools invented to help avoid unintended behaviour from code — code coverage.
Code coverage, first devised in the 1960s, encapsulates the idea that tests should ‘touch’ all of the code under test. If the tests execute all of your code, and the results from the tests are as expected, it is less likely your code contains unforeseen bugs. Untested code could do anything!
I will freely admit this is not a silver bullet. Writing tests achieving even 100% code coverage would not have caught the reentrancy bug that was the fatal flaw in the DAO unless someone had written a particularly inspired test. Indeed, blindly writing tests to achieve 100% coverage is probably not the best use of a developer’s time. Code coverage should only be treated as another arrow in our collective quiver.
