3 ms·

You're also talking about systems 20,000x larger than what The DAO contract was [1]. The total DAO contract is roughly 2,000 LOC by my estimate [2]. IMO it pro

You're also talking about systems 20,000x larger than what The DAO contract was [1]. The total DAO contract is roughly 2,000 LOC by my estimate [2]. IMO it probably won't be overly onerous to develop reliable contracts of this size using many of these techniques. It's just so few people have the discipline to delay implementation for design and planning at the level required when it needs to be bug free. Most software developers have no training in how to even begin designing and developing using these techniques. [1]: Shuttle's primary flight software contains 400,000 LOC http://www.nasa.gov/mission_pages/shuttle/flyout/flyfeature_shuttlecomputers.html http://www.nasa.gov/mission_pages/shuttle/flyout/flyfeature_... [2]: https://github.com/slockit/DAO https://github.com/slockit/DAO

egd 10y ago
> You're also talking about systems 20,000x larger than what The DAO contract was [1]. It sounds like the contract was underspecified. In my experience, the basic core logic of a system's usually a pretty small part of the overall codebase - the edge cases and error handling tend to be the bulk of the code. This tends to be the case in legal contracts, too - 100 pages of boilerplate to make sure the two pages of contract are air-tight.