![]() Like I said in another comment, there was no bug in Ethereum, there was a loophole in the DAO contract script. The issue arises when this implicit 'contract' is used to override the real contract - flying in the face of how Etherium claims to work.Ī much better solution would have been to try to address the underlying issues in Solidity - perhaps requiring future contracts to explicitly allow recursion? I personally question the decision to use a Turing-complete language to express contracts in the first place. The other contract is an implicit understanding of what the program 'should' do, and exists only in the minds of the creators of the contract. One contract is the program itself, which explicitly spells out what is and not allowed. More broadly, the hard-fork seems to imply that an Etherium contract is really made up of two contracts. The claim that the 'hacker' had 'stolen' funds from theDAO is ridiculous - you can only steal what doesn't belong to you, and ownership of theDAO's Ether is defined by the program itself! That is, an Etherium program doesn't implement a written contract, it is the contract.ĭespite this lofty goal, the core team saw fit to hard-fork the chain because they didn't like how a particular program was executing. The issue is, the person wasn't a 'hacker' in any meaningful sense of the word.Įtherium claims to be "a decentralized platform that runs smart contracts: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference" (from ). > Letting the hacker walk away with millions at that point would have been silly. In fact, it only strengthened my conviction and trust in the Ethereum project. I was not turned off in the least by the hard fork decision. In my view, the foundation and community handled the DAO debacle in a responsible, decentralized, open-minded, and respectful manner. I'm very pleased they didn't get their way. They never had the moral high ground nor the stronger end of the argument. The extremists, fundamentalists, and other ideologues who rallied to defend the theft because of their false notion of immutability and demented claims about "bailouts" never came close to understanding the severity of the situation. ![]() ![]() Despite all the ignorant comments and trolling, the truth is the HF worked out brilliantly. Consensus was achieved on this goal and the community resolved the situation as expected. In this sense, it was not a rollback as no other transactions were affected. That solution was to carefully recover all the funds from the attacker without creating any negative externalities on innocent bystanders. The simple fact is that the theft was significant enough to cause an unacceptable and pointless security risk to the network.įortunately for us, there was a built-in delay in the DAO contract which provided the foundation and community with enough time to engage in public debate and determine the best solution. I never invested in the DAO or cared about the investors. I supported the fork because it was the rational decision to make under the circumstances. undeniably has evolved to appear much more compelling in many ways for most players) World has moved on =) in an ironic twist it was MS' FOSS moves the last few months that sealed that perspective for me. ![]() And "FOSS developers" means "let's put some select libs/snippets of our SaaS on Github, it's zero risk/cost plus potential upside in terms of mindshare/image (and of course potentially genuinely useful to some out there, who aren't looking to (or going to manage to) clone us and hey may even contribute fixes or features)". It'll fade by the time the next gen are rushing in.ĭo these terms even mean much anymore? "Proprietary" means "our SaaS codebase isn't open-sourced but rest assured it's 80% FOSS on the inside anyway". Plus the youthful enthusiasm, I remember emulating and cultivating the hype speak from the late 90s / early 00s as a teen. Why do so many FOSS developers imitate the worst aspects of the proprietary, commercial software world?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |