Re:153k Ether Stolen in Parity Multi-Sig Attack
by kensai on Thursday July 20, 2017 @12:57AM
(#14810094)
Seriously, these observations should be submitted to the Solidity team for consideration.
[ Parent
| on HN ]
Re:153k Ether Stolen in Parity Multi-Sig Attack
by joncampbelldev on Thursday July 20, 2017 @01:02AM
(#14810106)
they are excellent observations, but it seems pretty clear the team would be unable to implement them properly this late in the game, or worse unable to understand why they are a good idea.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by federicobond on Thursday July 20, 2017 @10:30AM
(#14812747)
Most of these observations are well-known to the Solidity devs. I know because I participate in many of the conversations around it. While it's not easy to evolve a language (the API surface is pretty wide compared to many other programs), Solidity is indeed changing and improving regularly, only limited by the available time of their contributors.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by h1d on Thursday July 20, 2017 @09:57PM
(#14817550)
I thought they had enough funding to hire just about anyone.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by federicobond on Saturday July 22, 2017 @01:28AM
(#14825563)
I may have enough funding to pay more that Brendan Eich is making right now. That does not mean that he will join my project. Good talent is scarce regardless of funding.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by riffraff on Thursday July 20, 2017 @01:21AM
(#14810165)
Isn't the team also working on a new language targeting the same VM? If so, they might be useful.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by gst on Thursday July 20, 2017 @03:26AM
(#14810624)
There are lots of different languages targeting EVM. The (IMO) most promising so far is https://github.com/ethereum/viper
Re:153k Ether Stolen in Parity Multi-Sig Attack
by mbrock on Thursday July 20, 2017 @04:40AM
(#14810893)
You can also just write bytecode directly. It's a simple stack machine, and contracts should be as simple as possible.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by federicobond on Thursday July 20, 2017 @10:49AM
(#14812943)
Things are not always simpler at a lower level of abstraction.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by mbrock on Thursday July 20, 2017 @01:39PM
(#14814651)
It depends what simplicity you mean. The Solidity compiler is very far from simple, so if you consider that part of the complexity incurred by using Solidity, then a reasonably small bytecode program might be much easier to audit. Consider that a typical smart contract is as simple as "if four out of these six addresses make the same proposal then execute it." You can basically write these things in hexadecimal without too much trouble.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by federicobond on Saturday July 22, 2017 @01:39AM
(#14825592)
Yes, that's definitely a good idea. I will go back to my magnetized needle now, I have some bit flipping to do in order to finish my task for Monday.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by federicobond on Saturday July 22, 2017 @01:46AM
(#14825617)
Speaking seriously, there is an assembly for Ethereum called LLL. I would love to see code that performs exactly that example you mention and is easier to audit than the equivalent Solidity version.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by smoyer on Thursday July 20, 2017 @07:13AM
(#14811455)
For a stack machine, Forth might be a great choice.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by gradys on Thursday July 20, 2017 @02:26AM
(#14810411)
Can people outside of the Ethereum org implement their own languages that target that VM?