Timeline for What is the script assembly and execution in P2TR spend (spend from Taproot)
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2021 at 6:01 | comment | added | Dan | @Kalle, Wow... looks great, I'll check it out! I actually just finished hijacking some of the python in the bitcoin-core test_framework python just to replicate the pay-to-key key tweaks: reddit.com/r/Bitcoin/comments/r8wfio/… | |
| Dec 8, 2021 at 5:56 | comment | added | Kalle | FWIW, the 'tap' utility in btcdeb lets you create/manipulate -- and 'btcdeb' itself lets you examine details of -- taproot stuff, which may be helpful to learn how things fit together: github.com/bitcoin-core/btcdeb/blob/master/doc/… (disclaimer: I am the author) | |
| Dec 7, 2021 at 22:09 | vote | accept | Dan | ||
| Dec 4, 2021 at 21:42 | answer | added | Pieter Wuille | timeline score: 30 | |
| Dec 4, 2021 at 20:44 | comment | added | Dan | @PieterWuille, fair enough. Perhaps a better formed question: "What data does a node gather to validate a TXN attempting to spend a single-sig-P2TR output, and how does it use that data to do the validation?" | |
| Dec 4, 2021 at 20:00 | comment | added | Pieter Wuille | In the case of a P2TR key path spend, there are no scripts involved on chain at all (except the scriptPubKey with is just OP_1 <pubkey>, and an empty scriptSig). That's quite possibly what makes it hard to grasp, but also hard to answer your question as stated. | |
| Dec 4, 2021 at 19:25 | history | edited | Dan | CC BY-SA 4.0 |
correct grammar
|
| Dec 4, 2021 at 19:20 | history | asked | Dan | CC BY-SA 4.0 |