You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Account transactions require a key weight requirements be met. Generally one key will have enough weight to execute a TX but for "multi-sig" transactions a tool is needed to coordinate signatures within the applicable time window. This window is currently estimated at 10 minutes or so.
Suggested Solution
Current Solution
E-mailing/messaging signed messages around. Presumably this is the same method the ancient Romans used during their campaigns in gaul.
Proposed Solution
A SPA with realtime message based backend that will coordinate the above. A proposer will create a voucher that will be stored server side and be given a deep link to pass to others to allow them to sign.
@kerrywei commented on Wed Dec 08 2021
Issue To Be Solved
Problem
Account transactions require a key weight requirements be met. Generally one key will have enough weight to execute a TX but for "multi-sig" transactions a tool is needed to coordinate signatures within the applicable time window. This window is currently estimated at 10 minutes or so.
Suggested Solution
Current Solution
E-mailing/messaging signed messages around. Presumably this is the same method the ancient Romans used during their campaigns in gaul.
Proposed Solution
A SPA with realtime message based backend that will coordinate the above. A proposer will create a voucher that will be stored server side and be given a deep link to pass to others to allow them to sign.
@bluesign commented on Wed Dec 08 2021
I think it would be nice to have this on chain. onflow/service-account#66
The text was updated successfully, but these errors were encountered: