Re:153k Ether Stolen in Parity Multi-Sig Attack
by dom96 on Wednesday July 19, 2017 @06:27PM
(#14808560)
Wouldn't it make more sense to design it like Haskell? or something even more strict? A little bit of extra work seems like a small price to pay to prevent millions being stolen from your wallet because of a silly mistake like this...
[ Parent
| on HN ]
Re:153k Ether Stolen in Parity Multi-Sig Attack
by quickthrower on Wednesday July 19, 2017 @06:46PM
(#14808665)
In Haskell everything is public by default unless you specify exports for the module.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by aisofteng on Thursday July 20, 2017 @08:55AM
(#14812021)
But it also has a statically checked type system.
Re:153k Ether Stolen in Parity Multi-Sig Attack
by quickthrower on Thursday July 20, 2017 @07:45PM
(#14817118)
I think if done in Haskell how good or bad it is depends on the chosen abstraction for effects not Haskell itself.
Haskell is a good basis but the developers need to make the API fool proof. E.g. expose limited effects rather than a big fat "IO" type.