![Dr Maxim Orlovsky [LNP/BP] Profile picture](https://pbs.twimg.com/profile_images/378800000323264759/bce33bb0b7d54df04dd4b57630d110cf_bigger.jpeg)
#Taproot is coming. Each day before taproot activation I will publish mostly unknown tech insights into what taproot brings.
#1, pt 1/5. Taproot introduces new versioning for bitcoin script (as many know). But do you know that each taproot branch may have a different script?
#1, pt 1/5. Taproot introduces new versioning for bitcoin script (as many know). But do you know that each taproot branch may have a different script?
#1, pt 2/5. Moreover, taproot separates script versioning from witness versioning. I.e. in witness v5 we may have something like three script versions - or today v1 P2TR output may have a script condition for future versions of script
#1, pt 3/5. The new script versioning system is named *leaf version*. Current leaf version is 0xC0, meaning BIP-341, aka “Tapscript”. Yes, taproot can work not only with tapscript/BIP-341, but other future standards!
#1, pt 4/5. This means one can get taproot-based covenants like OP_TAPLEAF_UPDATE_VERIFY with another softfork but with no new witness version introduced – and it will work well with future witness softforks.
#1, pt 5/5. The strange version values, like 0xC0, are due to the fact that we need to distinguish witness elements in transaction inputs without knowing which version of witness it is - this we need not to use existing OP_CODE bytes. More to follow…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
