-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow multisig for non value transfer #58
base: master
Are you sure you want to change the base?
Conversation
Wouldn't a better solution be to always require multiple signatures if the |
hm, but calling a fallback function of another contract might also be something someone wants to do. |
The daily limit feature is not really useful once we have currency abstraction. I agree that with a daily limit of 0, every call (including send) should require multisig. |
another option would be to make |
@CJentzsch that sounds like a hack in order to do something that would be better as a parameter. I don't think the parameter should even exist, if you want to do something like signing a transaction to prove something then it's reasonable to require multiple signatures, since we can't really detect it. Another way to do it would be to create a more complex function that would analyze calls and allow or disallow them in a case by case question, but at that point it's so much complexity that we should simply adopt a DAO and you could add a "auto-manager" as one of the members. The future of the contract wallet is being a dao anyway. |
ok, but using |
Yes we should merge that. though it means a daily limit of 100 is actually only 99.9999999999... |
Daily limit of 100 but only allowing 99.99999 can be confusing for the user, who will want to send 100. I am in favor with @alexvandesande to always require multiple signatures when the data field is non empty, since using the value to check is no longer "safe" (may be tokens of greater value). That way we also satisfy @CJentzsch's point that a daily limit of 0 should mean "everything coming from the wallet signed by m_required members". I'll make this change and submit a pull request. |
Thanks @bencxr ! |
When using the multisig wallet for non value transfer purposes, it always requires only one signature since even with a daily limit of 0, a 0 value transfer transaction is "under the daily limit".
Using
<
instead of<=
solves the problem.The only downside is that the real daily limit which can be spend per day is
m_dailyLimit - 1 wei
.