5chdn

4 ms·

1.
by 5chdn 8y ago
Curious why people think so w.r.t. (2). Anyone can submit a proposal.
2.
by 5chdn 8y ago
EIP 867 which you are referring to is in limbo, this is not conforming with the ERP.
3.
by 5chdn 8y ago
Exactly. It is the library used by hundreds of wallets. The library itself does not hold any balance.
4.
by 5chdn 9y ago
Thanks for not reading the linked article, I'm explaining this very same example in the first paragraph :)
5.
by 5chdn 9y ago
lol :D
6.
by 5chdn 9y ago
But that's precisely my point. Pruned Ethereum nodes hold _all_ blocks and therefore are full nodes. In Ethereum, unlike pruning Bitcoin nodes, old blocks are not deleted.
7.
by 5chdn 9y ago
But a pruned bitcoin node does not hold the full blockchain for other nodes to download. A pruned Ethereum node, however, does.
8.
by 5chdn 9y ago
Miners are already incentivized not to mess with the state.
9.
by 5chdn 9y ago
Confirming this always was and still is the case. (Working for Parity.) However, this does not guarantee that such mistakes happen.
10.
by 5chdn 9y ago
Parity does not run on the EVM, it's a local node processing a local copy of the blockchain. You can create normal accounts which are just private/public keypairs you have full control of without anything "being in the cloud&
11.
by 5chdn 9y ago
Not directly, but Parity multi-signagure wallets on Ethereum Classic, Expanse, Musicoin, and other public chains are affected as well.
12.
by 5chdn 9y ago
Not at all. Solidity is just the most widely used language for the EVM. There are also Mutan (dead), Serpent (dying), LLL (recently revived), and Viper (being drafted).
13.
by 5chdn 9y ago
The code was reviewed by two other developers and this is the standard procedure for any pull request touching any of our code-base. The mistake that happened here, that security-relevant changes were not highlighted accordingly and should