Understanding Segwit and vBytes in Bitcoin

Been digging into segwit and soft forks. Why did we need vBytes? Seems like a way to avoid a hard fork. I heard it keeps a part of the transaction for old compatibility, which makes segwit transactions a bit heavier than P2PKH. So, is vBytes just a workaround to make segwit attractive?

Segwit actually changes the limit on transaction size by introducing a weight limit instead of a hard limit. It's a clever way to adapt while keeping everything compatible. Plus, the outputs have to stay accessible for nodes. Signatures can be discarded after processing, making them less of a burden long-term.

Exactly, vBytes are there because of how segwit transactions are structured. They count as virtual bytes. It adds some complexity but helps older nodes handle both types of transactions. More size, but it's about efficiency honestly.

Wait, so all parts still count? But the witness data doesn't get multiplied by 4 with vBytes? That sounds kinda confusing. I mean, what's the deal with that 4x discount?

It's the opposite! For nodes that aren’t segwit-ready, the witness data gets stripped out when sent. Usually, stripping data could break compatibility, but in segwit, the signature data is separate from the txid. That’s key for preventing malleability issues.

I get where you’re coming from, but gmaxwell really clarified it for me. This segwit trend is making more sense now, and I feel like it's a big step for Bitcoin.