pull down to refresh
2 replies \ @Murch 8 Oct \ on: REXEARCH : Virtual Size of Onchain Transaction bitcoin_beginners
Kudos for your efforts. Most of this looks good, but there are a few mistakes here and there. I’m prepping for the Optech Recap, so I’ll have to get back to this later, but I wanted to point out that a lot of the same information is compiled in topics tagged "transaction-weight" on Bitcoin Stack Exchange: https://bitcoin.stackexchange.com/questions/tagged/transaction-weight?tab=Frequent, e.g. https://bitcoin.stackexchange.com/a/75124/5406, https://bitcoin.stackexchange.com/questions/100159/what-is-the-size-and-weight-of-a-p2wpkh-input
few mistakes here and there
Damn i wronged the P2PK output size, the compressed one should've been 44 vB and the uncompressed one should've been 76 vB
Pay to Witness Script Hash (P2WSH). Input¹: variable (2-of-3: 105 vBytes)
I can't find any example of it with 105 vB input size yet
Pay to Taproot (P2TR). Scriptpath 2-of-3²: 82.75 vB–115.5 vB
This is out of my knowledge, for now i only know about keypath and 2-of-2 P2TR, interested to find these example i haven't found before but i have no tools to automate this (i do it manually)
Null Data (OP_RETURN). Output: x ≤ 83 + 11(?) bytes
Now that is something arbitrary lol, i decided to just write "≥ 34" as it is the simplest example of OP_Return output i can find
reply
I can't find any example of it with 105 vB input size yet
It’s really 418 weight units, which would translate to 104.5 vB, but the way vsize is defined, it’s supposed to be rounded up to the next integer. To be fair, I think I’ve been inconsistent on that one in the past years.
Pay to Taproot (P2TR). Scriptpath 2-of-3²: 82.75 vB–115.5 vB
This is out of my knowledge, for now i only know about keypath and 2-of-2 P2TR, interested to find these example i haven't found before but i have no tools to automate this (i do it manually)
I think the shortest nulldata output is 11 B.
reply