Hacker News Reader

Comment by mifeng | Hacker News Reader

Since contracts are immutable, you need modularity to be able to fix bugs like what happened with Parity. The problem is that Solidity libraries are also immutable, which means you can't fix them. The solution is easy: just use contract modules, not libraries.

View on HN

Parity actually used a contract module in this case.

No you don't. That's a myth.

Having modularity in these things only amplifies the damage when something DOES happen.

I'm not saying it is bad to have a centralized auditing of contracts, but I am saying it's not a good thing to simply import libraries and inherit some other abstract contract you don't fully understand when it comes to irreversible contracts.

This is a new type of problem we as a humanity have never faced before, so we need a different type of solution.

> This is a new type of problem we as a humanity have never faced before, so we need a different type of solution.

Could you elaborate on that? How is it a new problem? I would think it's similar to problems with hardware components or FPGA libraries, but maybe I'm missing something?

Crypto used to be a purely technological problem, which means if you have a secure cryptographic lock in your bank account and someone steals it from the bank, the bank is responsible to get it back to you.

But with cryptocurrencies, it's not just about technology but ties into other issues that normally have been tackled on a social level. So in this case there is no "bank" you can complain to or no one to sue.

Of course, you could say Ethereum as a whole can do a hard fork just for this, but that's another discussion altogether.

Reply on news.ycombinator.com