<p>I don’t think that there is a significant difference in terms of security between the various output types. Modern input types are more blockspace efficient, but a few wallets still <a href="https://whentaproot.org/" rel="nofollow noreferrer">cannot send to them</a>.</p>
<h2>P2PKH (aka Legacy)</h2>
<ul>
<li>Addresses start with <code>1…</code></li>
<li>All wallet software can parse the address format and send to it</li>
<li>148 bytes for an input, 34 bytes for an output</li>
</ul>
<h2>P2SH-P2WPKH (aka Wrapped Segwit)</h2>
<ul>
<li>Addresses start with <code>3…</code></li>
<li>All wallet software should be able to parse the address format and send to it</li>
<li>91 vbytes for an input, 32 bytes for an output</li>
</ul>
<h2>P2WPKH (aka Native Segwit (v0))</h2>
<ul>
<li>Addresses start with <code>bc1q…</code></li>
<li>Almost all wallet software can parse the address format and send to it</li>
<li>68 vbytes for an input, 31 bytes for an output</li>
</ul>
<h2>P2TR (aka Taproot (aka Native Segwit v1))</h2>
<ul>
<li>Addresses start with <code>bc1p…</code></li>
<li>Most wallet software can parse the address format and send to it, but a few services and wallets have <a href="https://whentaproot.org/#support" rel="nofollow noreferrer">not implemented support</a> yet.</li>
<li>57.5 vbytes for an input, 43 bytes for an output</li>
</ul>
<p>If you don’t mind occasionally dealing with a counterparty not being able to send to your standard addresses, I would just <a href="https://bitcoin.stackexchange.com/q/119301/5406">generally use P2TR</a>. For more compatibility, use P2WPKH. I would be surprised if someone had a convincing reason to recommend Legacy or Wrapped Segwit today.</p>

CC BY-SA 4.0
2024-08-13T19:51:10.203Z
2024-08-14T11:43:15.433Z
2024-08-14T11:43:15.433Z
Murch
<p>For better security and compatibility, using <strong>Native SegWit (bech32)</strong> is recommended for Bitcoin addresses. It offers lower fees and faster transaction processing. <strong>Taproot</strong> is more advanced, adding privacy and flexibility, but isn't as widely supported yet. Choose based on your needs and wallet compatibility!</p>

CC BY-SA 4.0
2024-08-13T07:14:55.870Z
2024-08-13T07:14:55.870Z
CoinChampion24
<p>Of the available address formats: Legacy, Segwit, Native segwit and Taproot</p>
<p>Which is the better one in terms of security?</p>
<p>What are the benefits of using one address over the other?</p>

<wallet><address>
What are the comparative benefits of each kind of address
Anuj Sanghvi
# What are the comparative benefits of each kind of address

(Asked by: username_0 on 2024-08-12)

Of the available address formats: Legacy, Segwit, Native segwit and Taproot

Which is the better one in terms of security?

What are the benefits of using one address over the other?

**Tags:** wallet, address


---

## 2 answers

### Answer by username_1 on 2024-08-13. Score: 3 | Accepted answer

I don’t think that there is a significant difference in terms of security between the various output types. Modern input types are more blockspace efficient, but a few wallets still [cannot send to them](https://whentaproot.org/).

## P2PKH (aka Legacy)

* Addresses start with `1…`
* All wallet software can parse the address format and send to it
* 148 bytes for an input, 34 bytes for an output

## P2SH-P2WPKH (aka Wrapped Segwit)

* Addresses start with `3…`
* All wallet software should be able to parse the address format and send to it
* 91 vbytes for an input, 32 bytes for an output

## P2WPKH (aka Native Segwit (v0))

* Addresses start with `bc1q…`
* Almost all wallet software can parse the address format and send to it
* 68 vbytes for an input, 31 bytes for an output

## P2TR (aka Taproot (aka Native Segwit v1))

* Addresses start with `bc1p…`
* Most wallet software can parse the address format and send to it, but a few services and wallets have [not implemented support](https://whentaproot.org/#support) yet.
* 57.5 vbytes for an input, 43 bytes for an output

If you don’t mind occasionally dealing with a counterparty not being able to send to your standard addresses, I would just [generally use P2TR](https://bitcoin.stackexchange.com/q/119301/5406). For more compatibility, use P2WPKH. I would be surprised if someone had a convincing reason to recommend Legacy or Wrapped Segwit today.


---

### Answer by username_2 on 2024-08-13. Score: 0

For better security and compatibility, using **Native SegWit (bech32)** is recommended for Bitcoin addresses. It offers lower fees and faster transaction processing. **Taproot** is more advanced, adding privacy and flexibility, but isn't as widely supported yet. Choose based on your needs and wallet compatibility!


---

