Bitcoin script is super powerful, like a programming language for the Bitcoin network. It's mainly used for transactions, where every output has a locking script and an unlocking script. You know, the ScriptPubKey and the ScriptSig.
Basically, scripts have two main elements: Opcodes and Data. Opcodes let you perform different actions on the data, which includes public keys and signatures.
True that! But when you're giving examples, don’t throw in a specific address. Like with P2PK, P2MS can't be shown as an address because it ain't wrapped in P2SH or P2WSH.
People call P2MS "Bare MultiSig," while the wrapped ones are referred to as "MultiSig." So let’s be clear: they should be called "P2SH-MultiSig" and "P2WSH-MultiSig."
Your example is related to P2SH. Try this one instead: 949591ad468cef5c41656c0a502d9500671ee421fadb590fbc6373000039b693.
Yeah, and besides P2WSH... low fees come from block size increases. Plus, the signatures get separated from the transaction hash. That’s known as witness data or witness, so yeah, you nailed it about Segwit vs Legacy.
You might wanna add some resources to your list. Like: address prefixes, Bitcoin Script reading list, and wallets that support output descriptors. Some might need the scripts and descriptors.
Don’t forget about P2WPKH-P2SH, aka the nested segwit script. It's a P2WPKH wrapped in a P2SH, which means it looks just like any other P2SH for older software.
I see your point. I was planning to stick to what I mentioned in my last thread, but since this is a compilation, it makes sense to include both nested segwits. Gonna start on that right away!