Skip to content
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

Translate Destination into script #1780

Open
iljakuklic opened this issue Jun 15, 2024 · 0 comments
Open

Translate Destination into script #1780

iljakuklic opened this issue Jun 15, 2024 · 0 comments
Labels

Comments

@iljakuklic
Copy link
Contributor

The Destination type is now included directly in the script. It could be broken down into its constituent parts during translation and represented in script explicitly:

  • The Signature script primitive to just take a pubkey / signature pair, verifying just one signature, rather than a destination.
  • The multisig destination is represented using the Threshold construct

This is slightly more versatile and unifies code paths between various ways of representing multisigs. Also more suitable to place on chain with a canonical way of encoding mutisig rather than having a choice between a threshold of signle sig destinations or a destination with a multisig in it.

There is also currently duplication in witness lookup by the signature verification function and the witness included in the script. This awkwardness would be resolved by having a canonical way of doing signature checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant