<p>P2WSH addresses have no deriving path since a P2WSH output does not send to a public key and P2WSH encodes a script, not a single public key.</p>

<p>Thanks to @Pieter Wuille for clearing up things. </p>

CC BY-SA 3.0
2018-03-10T16:46:57.323Z
2018-03-10T16:46:57.323Z
Tailer
<p>I know that the deriving path for Bech32 is 84, but what about P2WSH addresses path is it the same?</p>

<p>I've been reading <a href="https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki" rel="nofollow noreferrer">https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki</a> but nothing on there. </p>

<p>For example, I'm using path 84 to derive P2WSH addresses, but electrum uses that path to derive P2WPKH addresses. I would like to know the correct path that I should use, so my mnemonic phrase becomes compatible with other platforms. Something like 44 and 49 paths. </p>

CC BY-SA 3.0
2018-03-10T15:27:33.217Z
For what purpose? P2WSH moves coins under control of a script; what do you want that script to be?
Pieter Wuille
CC BY-SA 3.0
2018-03-10T15:38:30.157Z
I've made an edit showing usecase.
Tailer
CC BY-SA 3.0
2018-03-10T15:57:19.533Z
Perhaps my question wasn't clear: why do you need a P2WSH address? P2WSH encodes a _script_ not a single public key. Without good rationale this question makes little sense.
Pieter Wuille
CC BY-SA 3.0
2018-03-10T16:01:49.383Z
I read somewhere that P2WSH Address has a smaller size than P2WPKH; frankly, that's the main reason.
Tailer
CC BY-SA 3.0
2018-03-10T16:10:50.920Z
after reading that: https://bitcoincore.org/en/segwit_wallet_dev/#why-and-how-to-use-native-p2wpkh-and-p2wsh. I decided to not using P2WSH but the question still remains, is there's a specific path I should follow rather than 84 for P2WSH?
Tailer
CC BY-SA 3.0
2018-03-10T16:41:11.820Z
No, P2WSH is larger than P2WPKH, and *it does not serve the same purpose*. Your question makes no sense. A P2WSH output does not send to a public key.
Pieter Wuille
<bip32-hd-wallets><bech32-address>
Bech32-P2WSH BIP32 derivation path
Tailer
# Bech32-P2WSH BIP32 derivation path

(Asked by: username_0 on 2018-03-10)

I know that the deriving path for Bech32 is 84, but what about P2WSH addresses path is it the same?

I've been reading <https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki> but nothing on there.

For example, I'm using path 84 to derive P2WSH addresses, but electrum uses that path to derive P2WPKH addresses. I would like to know the correct path that I should use, so my mnemonic phrase becomes compatible with other platforms. Something like 44 and 49 paths.

**Tags:** bip32-hd-wallets, bech32-address

> **Comments:**
> **username_1**: For what purpose? P2WSH moves coins under control of a script; what do you want that script to be?  
> **username_0**: I've made an edit showing usecase.  
> **username_1**: Perhaps my question wasn't clear: why do you need a P2WSH address? P2WSH encodes a _script_ not a single public key. Without good rationale this question makes little sense.  
> **username_0**: I read somewhere that P2WSH Address has a smaller size than P2WPKH; frankly, that's the main reason.  
> **username_0**: after reading that: https://bitcoincore.org/en/segwit_wallet_dev/#why-and-how-to-use-native-p2wpkh-and-p2wsh. I decided to not using P2WSH but the question still remains, is there's a specific path I should follow rather than 84 for P2WSH?  
> **username_1**: No, P2WSH is larger than P2WPKH, and *it does not serve the same purpose*. Your question makes no sense. A P2WSH output does not send to a public key.  

---

## 1 answers

### Answer by username_0 on 2018-03-10. Score: 2 | Accepted answer

P2WSH addresses have no deriving path since a P2WSH output does not send to a public key and P2WSH encodes a script, not a single public key.

Thanks to @username_1 for clearing up things.


---

