<blockquote>
  <p>I might be understanding this incorrectly, but it sounds like the users and/or wallet custodian (coinbase, blockchain.info, etc) must create a P2SH-P2WPKH addresses in order for the witness data to be segregated and save on block space.</p>
</blockquote>

<p>Correct, you first have to receive money to a SegWit address. Witness space can only be used when spending outputs received on a SegWit address. The bitcoins can be sent to any type of address from a SegWit input, though.</p>

<blockquote>
  <p>Does the new release 0.13.1 default to creating P2WPKH addresses or will the users and online wallet providers have to do this manually? Will there be a built-in RPC function for creating these addresses similar to createmultisig ?</p>
</blockquote>

<p><strong>SegWit transactions created before the activation of SegWit could lead to permanent loss of funds</strong>, therefore, 0.13.1 will not create SegWit addresses or transactions by default.</p>

<p>→ Please consider the section <a href="https://bitcoincore.org/en/segwit_wallet_dev/#upgrade-safety" rel="nofollow noreferrer">Upgrade Safety</a> in Bitcoin Core's SegWit Wallet Developer Guide carefully.</p>

CC BY-SA 3.0
2016-10-27T20:45:52.803Z
Sorry, I am just realizing how useless this answer is. :p Waiting for a better one, so I can delete mine. ;)
Murch
CC BY-SA 3.0
2016-10-27T20:46:59.183Z
Don't delete! I had no idea about "SegWit transactions created before the activation of SegWit could lead to permanent loss of funds" and I'm sure I'm not the only one.
m1xolyd1an
CC BY-SA 3.0
2016-10-27T20:48:55.460Z
@m1xolyd1an: The transaction script looks like `anyone can spend` to miners not updated to SegWit. SegWit transactions are only safe to broadcast to the network once it has been activated, as then miners will reject blocks that treat SegWit transactions not as SegWit transactions.
Murch
CC BY-SA 3.0
2016-10-27T20:41:21.807Z
2017-07-07T20:57:44.017Z
2017-07-07T20:57:44.017Z
Murch
<p>I'm going through this guide: <a href="https://bitcoincore.org/en/segwit_wallet_dev/" rel="nofollow">https://bitcoincore.org/en/segwit_wallet_dev/</a></p>

<p>I might be understanding this incorrectly, but it sounds like the users and/or wallet custodian (coinbase, blockchain.info, etc) must create P2SH-P2WPKH addresses in order for the witness data to be segregated and save on block space.  According to the guide, soon after activation only a limited number of segwit transactions will be on the network. </p>

<p>Does the new release 0.13.1 default to creating P2WPKH addresses or will the users and online wallet providers have to do this manually?  Will there be a built-in RPC function for creating these addresses similar to <code>createmultisig</code> ?</p>

<segregated-witness><p2wpkh>
Using segwit and creating Pay-To-Witness (P2WPKH) addresses
m1xolyd1an
# Using segwit and creating Pay-To-Witness (P2WPKH) addresses

(Asked by: username_0 on 2016-10-27)

I'm going through this guide: <https://bitcoincore.org/en/segwit_wallet_dev/>

I might be understanding this incorrectly, but it sounds like the users and/or wallet custodian (coinbase, blockchain.info, etc) must create P2SH-P2WPKH addresses in order for the witness data to be segregated and save on block space. According to the guide, soon after activation only a limited number of segwit transactions will be on the network.

Does the new release 0.13.1 default to creating P2WPKH addresses or will the users and online wallet providers have to do this manually? Will there be a built-in RPC function for creating these addresses similar to `createmultisig` ?

**Tags:** segregated-witness, p2wpkh


---

## 1 answers

### Answer by username_1 on 2016-10-27. Score: 2 | Accepted answer

> I might be understanding this incorrectly, but it sounds like the users and/or wallet custodian (coinbase, blockchain.info, etc) must create a P2SH-P2WPKH addresses in order for the witness data to be segregated and save on block space.

Correct, you first have to receive money to a SegWit address. Witness space can only be used when spending outputs received on a SegWit address. The bitcoins can be sent to any type of address from a SegWit input, though.

> Does the new release 0.13.1 default to creating P2WPKH addresses or will the users and online wallet providers have to do this manually? Will there be a built-in RPC function for creating these addresses similar to createmultisig ?

**SegWit transactions created before the activation of SegWit could lead to permanent loss of funds**, therefore, 0.13.1 will not create SegWit addresses or transactions by default.

→ Please consider the section [Upgrade Safety](https://bitcoincore.org/en/segwit_wallet_dev/#upgrade-safety) in Bitcoin Core's SegWit Wallet Developer Guide carefully.

> **Comments:**
> **username_1**: Sorry, I am just realizing how useless this answer is. :p Waiting for a better one, so I can delete mine. ;)  
> **username_0**: Don't delete! I had no idea about "SegWit transactions created before the activation of SegWit could lead to permanent loss of funds" and I'm sure I'm not the only one.  
> **username_1**: @username_0: The transaction script looks like `anyone can spend` to miners not updated to SegWit. SegWit transactions are only safe to broadcast to the network once it has been activated, as then miners will reject blocks that treat SegWit transactions not as SegWit transactions.  

---

