<blockquote>
  <p>Until a P2SH-P2WPKH UTXO is spent and the redeemScript is exposed, a P2SH-P2WPKH address is indistinguishable from a non-segwit P2SH address (such as a non-segwit multi-signature address)</p>
</blockquote>

<p>Reference: <a href="https://bitcoincore.org/en/segwit_wallet_dev/" rel="noreferrer">https://bitcoincore.org/en/segwit_wallet_dev/</a></p>

<p>That's because a P2SH address is still a <em>hash</em> of the script, regardless of whether the script is an embedded P2WPKH script or plain old script script. So you can't 'decode' it back into what the script is, you have to wait until the script itself is made public when redeeming the output.</p>

CC BY-SA 3.0
2017-08-25T14:18:30.817Z
yup, type 3 addresses are a hash of an input value, and with current technology it is nearly impossible, to reverse the function to see it's initial input.
pebwindkraft
CC BY-SA 3.0
2017-08-25T12:51:55.100Z
2017-08-25T12:51:55.100Z
meshcollider
<p>Let there be an address <code>3ABCDEFGHJKDJHDH....</code></p>

<p>How can I understand if it's a SegWit address or a MultiSig address?</p>

<segregated-witness><multi-signature><p2sh>
Difference between a SegWit address and a P2SH address
MCCCS
# Difference between a SegWit address and a P2SH address

(Asked by: username_0 on 2017-08-25)

Let there be an address `3ABCDEFGHJKDJHDH....`

How can I understand if it's a SegWit address or a MultiSig address?

**Tags:** segregated-witness, multi-signature, p2sh


---

## 1 answers

### Answer by username_1 on 2017-08-25. Score: 8 | Accepted answer

> Until a P2SH-P2WPKH UTXO is spent and the redeemScript is exposed, a P2SH-P2WPKH address is indistinguishable from a non-segwit P2SH address (such as a non-segwit multi-signature address)

Reference: <https://bitcoincore.org/en/segwit_wallet_dev/>

That's because a P2SH address is still a *hash* of the script, regardless of whether the script is an embedded P2WPKH script or plain old script script. So you can't 'decode' it back into what the script is, you have to wait until the script itself is made public when redeeming the output.

> **Comments:**
> **username_2**: yup, type 3 addresses are a hash of an input value, and with current technology it is nearly impossible, to reverse the function to see it's initial input.  

---

