-
Notifications
You must be signed in to change notification settings - Fork 1k
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
CreateStandardMultisigAccount interop #2342
Labels
discussion
Initial issue state - proposed but not yet accepted
Comments
roman-khimov
added
the
discussion
Initial issue state - proposed but not yet accepted
label
Feb 16, 2021
Since there is a need for this Native embedded feature I think it is worth implementing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary or problem description
There is a
System.Contract.CreateStandardAccount
interop that converts given key into standard script hash, but we can't do the same for multisig accounts which can also be useful. Multisig scripts are much more complex than single-signature scripts, so implementingCreateMultiSigRedeemScript
in smart contract is time-consuming and error-prone.The need to calculate proper multisig script hash is relevant for NeoFS governance scheme implementation (#2267) combined with P2P Notary system (#1573), we have all inner ring node keys in the contract, but we need to check for multisig witness of these keys.
The same problem can occur with role management contract which has
GetDesignatedByRole
method returning key array, so the user of this method can get this array but can't easily derive multisig script hash from it.Do you have any solution you want to propose?
Provide
System.Contract.CreateStandardMultisigAccount
interop that will have the same input parameters asCreateMultiSigRedeemScript
method (number of valid signatures required and a list of keys) and will return script hash to the caller.Neo Version
Where in the software does this update applies to?
The text was updated successfully, but these errors were encountered: