Validation of segwit v0-v1 tx routinely provides OP_CHECKSIG?

on

|

views

and

comments


Once I create a segwit transaction v0 (P2WPKH) or v1 (P2TR key-path spend) I do like that (let’s spend a P2TR output):

  • Locking Script (of the P2TR output I am spending): OP_1 PK_size PK
  • Witness: 1 (witness_count) SIG_size SIG

So I am questioning, the op code CHECKSIG is routinely added when nodes confirm this transaction?

As a result of with legacy P2PKH transaction you’ve got:

  • Locking Script (of the P2PKH output I am spending): dup + hash_160 + pk_hash_size + pk_hash + equalverify + checksig
  • Unlocking Script: SIG_size SIG PK_size PK

So on this case (P2PKH) there explicitly is the OP_CHECKSIG within the locking script.

Thanks upfront!

Share this
Tags

Must-read

Self-driving taxis are coming to London – ought to we be anxious? | Jack Stilgoe

At the top of the nineteenth century, the world’s main cities had an issue. The streets had been flooded with manure, the unintended...

US regulators open inquiry into Waymo self-driving automobile that struck youngster in California | Expertise

The US’s federal transportation regulator stated Thursday it had opened an investigation after a Waymo self-driving car struck a toddler close to an...

US robotaxis bear coaching for London’s quirks earlier than deliberate rollout this yr | London

American robotaxis as a consequence of be unleashed on London’s streets earlier than the tip of the yr have been quietly present process...

Recent articles

More like this

LEAVE A REPLY

Please enter your comment!
Please enter your name here