Timeline for Watch-only addresses inside segwit transactions
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 17, 2019 at 7:45 | comment | added | Miloš Samardžija | I've added all the steps into my first post. | |
Jan 17, 2019 at 7:43 | history | edited | Miloš Samardžija | CC BY-SA 4.0 |
added 4270 characters in body
|
Jan 16, 2019 at 15:57 | comment | added | Pieter Wuille | Please describe in details all the steps and RPCs you are using. The raw transaction API certainly supports creating segwit spends, but can be annoying to use. | |
Jan 16, 2019 at 8:00 | comment | added | Miloš Samardžija | The problem is that signrawtransactionwithkey also returns a non-segwit transaction (flag for segwit in encoded transaction is not active). | |
Jan 16, 2019 at 6:53 | comment | added | Pieter Wuille | The fact that createrawtransaction does not give you a segwit-encoded output is completely expected, as it has no witness. That's not a problem; signrawtransaction will happily take it, and add a witness if needed, and return a transaction in segwit format in that case. | |
Jan 15, 2019 at 16:28 | history | edited | Miloš Samardžija | CC BY-SA 4.0 |
added 349 characters in body
|
Jan 15, 2019 at 16:21 | history | edited | Miloš Samardžija | CC BY-SA 4.0 |
added 88 characters in body
|
S Jan 15, 2019 at 16:15 | history | suggested | Glorfindel |
tags edited
|
|
Jan 15, 2019 at 16:12 | review | Suggested edits | |||
S Jan 15, 2019 at 16:15 | |||||
Jan 15, 2019 at 16:10 | history | migrated | from crypto.stackexchange.com (revisions) | ||
Jan 15, 2019 at 16:06 | history | asked | Miloš Samardžija | CC BY-SA 4.0 |