-
Notifications
You must be signed in to change notification settings - Fork 176
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
Add witness option to input-set command. #644
Comments
Original tx:
|
Desired script:
|
Explorer's |
The multi-token nature of the input-set |
For consistency the witness should be provided unencoded, as a set of bracketed data tokens (without prefix). This is the canonical textual serialization provided by |
Thank you for looking into this issue and taking it up as an enhancement. --witness (-w) is the cleanest way as far as I can see too. Lack of this feature in bx is a deal breaker for people relying on bx and still wanting to try Segwit and second level protocols that are now possible. I understand you are pushing it as an enhancement for next release and 4.0 has a lot of Segwit related enhancements as I can see. Any time line you are thinking of for this so that I can help test etc. |
I am waiting for this issue to be resolved and I also want to help with the development of such a useful tool. Adding a bounty :-) Anyone... please make this happen! /boss $1000 |
I am not sure why this Bounty app is not working... sorry for posting multiple times... The promise holds good if this enhancement is committed in the next 7 days. I can do PayPal. Thank you for understanding. |
I thought it was 1000 sats :). I am tempted to raise a little money for the Libbitcoin Institute. Maybe tonight when I finish up with taproot signature hashing, unless someone else wants to take it. |
Also... do we need any changes to As far as I know and understanding, no changes are required but some one more knowledgeable in this can clarify please... |
Any updates? @evoskuil Eric are you attempting this enhancement? |
Sorry, got a little sidetracked, and now I’m traveling for a few days. I decided to finish up taproot before taking on something new. Bu if nobody grabs this I’ll pick it up. |
@evoskuil, hi, do you still have plans on implementing it sometimes? And if it's backlogged what is the best alternative to bx to generate segwit transactions currently? |
Hi @j1warren - I’m not up on alternative tooling, sorry. It is definitely planned, and also a bit backlogged while I get my shit together, and while other contributors are busy making money. |
@evoskuil Hello Eric... Any updates on this enhancement? |
No :/ |
I am able to generate signatures using input-sign for a segwit transaction created using bitcoin-cli
HEX: 0200000001a7be5c74cb963c426e295a3f145bf397d8d7c12711bbb2bb6dcb318a505465de0000000000ffffffff01c0e4022a0100000017a9140a37ed6a88d66dc102bde8a6a299b44c81daa7178700000000
But not able to add them in a segwit compatible way using input-set. This is what I am getting after constructing and adding the endorsement script which does not look like a segwit transaction.
Is it even supported? I built bx by checking out the master branch today.
The text was updated successfully, but these errors were encountered: