Permalink
Browse files

Fix initialisation bug.

  • Loading branch information...
gavofyork committed Jul 19, 2017
1 parent c647963 commit e06a1e8dd9cfd8bf5d87d24b11aee0e8f6ff9aeb
Showing with 7 additions and 4 deletions.
  1. +1 −1 js/src/contracts/code/wallet.js
  2. +6 −3 js/src/contracts/snippets/enhanced-wallet.sol
Oops, something went wrong.

10 comments on commit e06a1e8

@admazzola

This comment has been minimized.

Show comment
Hide comment
@admazzola

admazzola Jul 19, 2017

Who is auditing this code that ends up affecting $100 millions worth of currency ? :/

admazzola replied Jul 19, 2017

Who is auditing this code that ends up affecting $100 millions worth of currency ? :/

@3esmit

This comment has been minimized.

Show comment
Hide comment
@3esmit

3esmit Jul 19, 2017

Why save addresses as uint? This contracts seems to be overcomplicated to what it wants to do. See Consensys Multisig, they have a much simplier approch.

3esmit replied Jul 19, 2017

Why save addresses as uint? This contracts seems to be overcomplicated to what it wants to do. See Consensys Multisig, they have a much simplier approch.

@jomo

This comment has been minimized.

Show comment
Hide comment
@jomo

jomo Jul 20, 2017

@admazzola This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

jomo replied Jul 20, 2017

@admazzola This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

@benjyz

This comment has been minimized.

Show comment
Hide comment
@benjyz

benjyz Jul 20, 2017

@jomo license needs fixing. if there is no "warranty" or any promise of security at all, then use of this software should be actively discouraged. GNU is very likely not a good license for a cryptocurrency wallet. question about audits is reasonable.

benjyz replied Jul 20, 2017

@jomo license needs fixing. if there is no "warranty" or any promise of security at all, then use of this software should be actively discouraged. GNU is very likely not a good license for a cryptocurrency wallet. question about audits is reasonable.

@TheNikomo

This comment has been minimized.

Show comment
Hide comment
@TheNikomo

TheNikomo Jul 20, 2017

@benjyz You would not have access to this code if the no-warranty clause did not exist. Nobody's going to accept personal responsibility for freely-provided code that they may or may not be properly compensated for writing.

I'm also not seeing you volunteer to provide cash to insure every single deployed multisig contract.

TheNikomo replied Jul 20, 2017

@benjyz You would not have access to this code if the no-warranty clause did not exist. Nobody's going to accept personal responsibility for freely-provided code that they may or may not be properly compensated for writing.

I'm also not seeing you volunteer to provide cash to insure every single deployed multisig contract.

@maaaaark

This comment has been minimized.

Show comment
Hide comment
@maaaaark

maaaaark Jul 20, 2017

@admazzola I understand your frustration, but here's why I think it's being misdirected. This is an open source project that offers a wallet. Ethereum-based blockchain projects are choosing to run their ICO's on a multi-sig wallet that this project generates. Don't you think it should be up to the team behind the ICO to do whatever necessary to make sure that their ICO smart contract is secure?

maaaaark replied Jul 20, 2017

@admazzola I understand your frustration, but here's why I think it's being misdirected. This is an open source project that offers a wallet. Ethereum-based blockchain projects are choosing to run their ICO's on a multi-sig wallet that this project generates. Don't you think it should be up to the team behind the ICO to do whatever necessary to make sure that their ICO smart contract is secure?

@dissaranged

This comment has been minimized.

Show comment
Hide comment
@dissaranged

dissaranged Jul 20, 2017

would it make sense to have solidity default each function, that is not explicit external or public to internal?

Then this would not have happend :)

dissaranged replied Jul 20, 2017

would it make sense to have solidity default each function, that is not explicit external or public to internal?

Then this would not have happend :)

@persicsb

This comment has been minimized.

Show comment
Hide comment
@persicsb

persicsb Jul 21, 2017

Internal is default per the docs.
"By default, function types are internal, so the internal keyword can be omitted."
http://solidity.readthedocs.io/en/develop/types.html#function-types

Is it a compiler bug?

persicsb replied Jul 21, 2017

Internal is default per the docs.
"By default, function types are internal, so the internal keyword can be omitted."
http://solidity.readthedocs.io/en/develop/types.html#function-types

Is it a compiler bug?

@SCBuergel

This comment has been minimized.

Show comment
Hide comment
@SCBuergel

SCBuergel Jul 21, 2017

AFAIK that is not true and a documentation bug...
I reported this: ethereum/solidity#2617

SCBuergel replied Jul 21, 2017

AFAIK that is not true and a documentation bug...
I reported this: ethereum/solidity#2617

@admazzola

This comment has been minimized.

Show comment
Hide comment
@admazzola

admazzola Jul 21, 2017

This is only the opinion of one person but I also feel as though it would be prudent to make the functions default to internal in the next version of the solidity compiler. This is the way Java works; classes default to private if it is not explicitly stated to make them public. See you can't get in trouble with a private method, it just wont work at all.

admazzola replied Jul 21, 2017

This is only the opinion of one person but I also feel as though it would be prudent to make the functions default to internal in the next version of the solidity compiler. This is the way Java works; classes default to private if it is not explicitly stated to make them public. See you can't get in trouble with a private method, it just wont work at all.

Please sign in to comment.