Live data from Hacker News

Critical Update on DAO Vulnerability

blog.ethereum.org

221–230 of 629 posts

Re: Critical Update on DAO Vulnerability

#221

developer asks token holders to spam the network to delay the attack o.O griff [10:05 AM] @channel The DAO is being attacked. It has been going on for 3-4 hours, it is draining ETH at a rapid rate. This is not a drill. You can help: If anyone knows who has the split proposals Congo Split, Beer Split and FUN-SPLT-42, please DM me We need their help! If you want to help, you can vote yes on those aforementioned split p…

BRIGHTEST MINDS.

Re: Critical Update on DAO Vulnerability

#222
post #211

Earlier quoted context omitted.

This argument can be made for most/all software vulnerabilities.

I am not sure. I believe that in many cases similar activity would illegal or at least forbidden by Terms and Conditions. I the DAO case I am not aware of any regulations or laws that the "attacker" has broken.

The DAO's 'terms and conditions' were the contract code itself. During the crowd sale, it was often said that 'investors' need to look at the code because that is the only binding agreement. I guess it turns out that's a lie too.

Re: Critical Update on DAO Vulnerability

#223

This is what concerns me about contract programming. With human contract law, if there's a minor typo or loophole, participants can generally see the spirit and intent, and at worst go to a judge who will usually enforce the intent. But with software contracts, only the characters matter and there's no intent anywhere: either you get paid or you don't. ETH is advising, "Contract authors should ... be very careful abo…

> How do _you_ know your contract is secure?

It most likely is not, looking at the recent post on contract security, most if not all examples ever posted as best practice are flawed and can be exploited:

https://blog.ethereum.org/2016/06/10/smart-contract-security... (currently down, cached version https://webcache.googleusercontent.com/search?q=cache:https:...)

Re: Critical Update on DAO Vulnerability

#225
post #211

Earlier quoted context omitted.

This argument can be made for most/all software vulnerabilities.

I am not sure. I believe that in many cases similar activity would illegal or at least forbidden by Terms and Conditions. I the DAO case I am not aware of any regulations or laws that the "attacker" has broken.

And as such, the contract would include clauses to protect against that. If the contract did not, one of the parties likely can take advantage as they wish.

It is the same with Ethereum. If the DAO 'contract' does not include the terms, the 'lawyer' who wrote it just didn't do a very good job and it is open to taking advantage.

Re: Critical Update on DAO Vulnerability

#226

The provided link is just a page showing a bunch of transactions. For someone like me, who is not so intimate with the Ethereum terminology in use (but who is still interested in the DAO, as an observer), could someone provide a layman's explanation of what's going on? Somewhat more specifically, I'm wondering the following: - At a high level, what does this attack actually consist of? - How does ethereum "go missing…

> - At a high level, what does this attack actually consist of? At a high level, The Dao is like Pokemon. Casual observation suggests that it may be a more or less consistent world internally and that a lot of people are very excited about it. A few of those people even claim to fully understand how it works. But there's a lot of fat guys with acne blindly spending on Pokemon cards thinking it's a wise investment. Un…

Finally, an explanation of ethereum that makes sense!

Re: Critical Update on DAO Vulnerability

#227

This is what concerns me about contract programming. With human contract law, if there's a minor typo or loophole, participants can generally see the spirit and intent, and at worst go to a judge who will usually enforce the intent. But with software contracts, only the characters matter and there's no intent anywhere: either you get paid or you don't. ETH is advising, "Contract authors should ... be very careful abo…

I agree completely. 'Smart' contracts are terribly flawed in this regard. Operating outside of contract law is a weakness, not a strength.

No-one can write bug-free code, so why are these people building a huge, expensive system that relies on no bugs being found?

Re: Critical Update on DAO Vulnerability

#228

Can someone eli5 what DAO and ethereum are?

Cryptocurrencies are digital tokens. Ownership of these digital tokens are kept in a ledger called a blockchain. Every transaction or transfer of tokens is recorded in the blockchain. Everyone can also see the blockchain as it is a public ledger. Both Bitcoin and Ether are cryptocurrencies. Bitcoin was the first to demonstrate blockchain technology. In practice, these tokens function like programmable money. However the usefulness of Bitcoin is limited. Ethereum was developed to expand the original concept so more things could be done with these digital tokens. Ethereum made the programmable tokens more powerful with features like smart contracts. It is worth noting that each cryptocurrency has its own blockchain which can be confusing.

DAO is an autonomous corporation that runs on top of Ethereum. The digital token in the Ethereum ecosystem is called Ether. So the DAO raised somewhere around ~$150M USD in equivalent Ether funds during its IPO-like phase.

Re: Critical Update on DAO Vulnerability

#229

I have a (maybe naive) question: why is the person draining ETH from DAO called "attacker"? I seems to me that the idea behind smart contracts was to have unambiguous description of what are participants agreeing to. The "attacker" is doing precisely this - I had not heard of any bug in Ethereum implementation that is used, only "bug" in DAO's smart contract. So he is allowed to do this, by contract definition. Isn't…

Welcome to real life, where that's exactly how contracts, contract law and disputes over contracts work.
Post reply on HN