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
One useful feature, already proposed for Neo 2 (#700 but now not in schedule for implementation) is the ability to check multiple witness in a "multisig" format. This gives flexibility to Witness scripts, at the same time it allows composition in a "multisig" manner.
Using this, each consensus node could be itself a MultiSig contract, or any other verification mean, and still make part of a global multisig contract.
Even with Schnorr signatures in the future, I still think this is a better approach (for very small number of signatures), because it allows all parties to maintain their own control over "share on multisignature contract". Many may use Schorr because of extra privacy too, although not possible here because verifications will eventually be exposed (not the case for Schnorr contracts). But Schnorr will be limited to classic pubkey logic (good for several consensus nodes).
On general, I think that a Governance Script could allow consensus nodes to update their pubkeys (part of Schnorr sig in the future), and votes would go to this governance contract. So they would have full control on contract rules (including changing consensus pubkey), as bigger entities or even independent groups sharing a single govenance contract.
One useful feature, already proposed for Neo 2 (#700 but now not in schedule for implementation) is the ability to check multiple witness in a "multisig" format. This gives flexibility to Witness scripts, at the same time it allows composition in a "multisig" manner.
Using this, each consensus node could be itself a MultiSig contract, or any other verification mean, and still make part of a global multisig contract.
Example:
Witness A (scripthash1):
Witness B (scripthash3):
Witness C:
This should pass, because we require 2/3 witness, and scripthash1 and scripthash3 will be fulfilled :)
The text was updated successfully, but these errors were encountered: