reply on: REXEARCH : Virtual Size of Onchain Transaction \ stacker news ~bitcoin

172 sats \ 1 reply \ @Rexdentron OP 8 Oct \ parent \ on: REXEARCH : Virtual Size of Onchain Transaction bitcoin_beginners

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

If i had found these 1, 2 post before it would make my life so much easier. Much grateful for your contribution to the community🫡

266 sats \ 0 replies \ @Murch 8 Oct

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)

Check out https://murch.one/posts/2-of-3-using-p2tr/

I think the shortest nulldata output is 11 B.