P2WPKH (Pay-to-Witness-PubKey-Hash): The Anchor Guide to Native SegWit

🔍 Why This Module Matters

If you want to use Bitcoin efficiently in the 21st century, you use P2WPKH. It is the "Native" version of SegWit that skips the backward-compatibility wrappers and goes straight for maximum performance. This module will deconstruct the architecture of the bc1q address, explain why spending from a P2WPKH input is the cheapest possible single-key operation, and detail the "Bech32" encoding that makes typos nearly impossible.

🏛️ The "Native" Difference: Removing the Wrapper

There are two ways to use SegWit: Nested and Native.

1. Nested SegWit (The Bridge)

• Address: Starts with 3.

• Logic: It "wraps" the SegWit instructions inside a legacy P2SH script so that old software can still understand it.

• Burden: It carries extra "Redeem Script" bytes that increase the cost of a transaction.

2. Native SegWit (The Destination)

• Address: Starts with bc1q.

• Logic: It uses the SegWit versioning directly. No wrapping, no extra bytes.

• Benefit: This is the "Purest" and cheapest form of SegWit. It is the most space-efficient way to move single-key bitcoin on the network today.

⚙️ Bech32: The Superior Address Format

P2WPKH abandoned the old Base58 encoding in favor of Bech32 (BIP 173).

The Checksum: Bech32 can detect up to 4 errors in an address. It is mathematically designed so that if you accidentally swap two characters, the address is guaranteed to be invalid.

🛠️ The Witness Area: Where the Data Lives

In a legacy transaction, your signature is in the middle of the data. In P2WPKH, the ScriptSig field is 0 Bytes (Empty).

• The Move: The Node says: "I see this is a bc1q address. I won't look for the signature in the input. I will look for it in the Witness stack at the end of the transaction."

• The Discount: Because the signature is in the Witness area, it only "counts" as 1/4 of its actual weight toward the block size limit. This is the source of the SegWit fee discount.

graph LR
 subgraph Transaction_Core
 A[Inputs: Empty ScriptSig]
 B[Outputs]
 end
 subgraph Witness_Area
 C[Signature]
 D[Public Key]
 end
 A --> C
 A --> D
 style Witness_Area fill:#f96,stroke:#333,stroke-width:2px

🛡️ Privacy and Efficiency: Why it is the Standard

1. Cheaper Fees: Spending a P2WPKH output is roughly 30-40% cheaper than spending a Legacy output.

2. Malleability Fix: Because the signature is "segregated," the Transaction ID (TXID) cannot be changed by third parties. This is what made the Lightning Network possible.

3. Modern Identity: Using bc1q signals to the network that you are a modern participant using the latest security and efficiency standards.

🎯 Learning Objectives for this Module

By the end of this module, you will be able to:

1. Define P2WPKH and identify its native address prefix (bc1q).

2. Explain the difference between "Nested" and "Native" SegWit.

3. Identify three advantages of the Bech32 address format over Base58.

4. Describe the role of the empty ScriptSig in a Native SegWit spend.

5. Understand why P2WPKH transactions are cheaper than any other single-key type.

🗺️ Module Roadmap: What's Next?

Now that we've seen the "Native" future, we will look at the bytes:

1. P2WPKH ScriptPubKey Structure: Deconstructing the Version 0 Witness Program.

2. The Witness Stack: How signatures are serialized at the end of the TX.

3. Bech32 Encoding (BIP 173): A technical look at the polynomial checksum.

4. Python P2WPKH Auditor: Writing a script to derive a bc1q address from a raw pubkey.

🎓 Summary

P2WPKH is the peak of single-key efficiency in Bitcoin. It represents the successful transition of the protocol into a more scalable, secure, and user-friendly era. By mastering Native SegWit, you are understanding the current "Gold Standard" of Bitcoin transactions and the technical foundation upon which all modern layer-2 scaling solutions are built.