Open
Conversation
Give a rough outline and links to the places that demand the scriptPubKey to be exactly as described in the bitcoin developer guide
One of the two previous proposals was a 1-of-3 multisig where the third public key would be artificially generated along with proof that a corresponding private key is unknown and would play the role of the TIR transaction tag. This however would be susceptible to a lucky attacker who could find a corresponding private key and be able to spend all TIR transactions. Christos proposed to replace the above with a 2-of-3 multisig with a publicly known private key for the tag. This way TIR transactions are future-proof against the previously described atttack and correctly emulate the 1-of-2 desired behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.