<p>There are no "addresses" in protocol. There are only "output scripts". The address is only human-readable representation of script which matches the "output script".</p>

<p>The output script for bare multisig transaction is [m] + [hash1] + [hash2] + ... + [hashN] + [n] </p>

<p>And all of these parts are significant. There is no "classic" representation of such address yet.</p>

<p>bc.i uses the form of <strong>(Escrow X of X1 X2 X3)</strong> (where Xn is standard p2pkh address) but you may use your own.</p>

CC BY-SA 3.0
2014-08-08T20:54:15.013Z
So bare multisig transactions do not have "addresses"?
user18688
CC BY-SA 3.0
2014-07-30T03:51:45.243Z
2014-07-30T04:21:34.927Z
2014-07-30T04:21:34.927Z
amaclin
<p>In P2SH transactions, the address is the hash of the redeemScript. What is it for P2PKH transactions?</p>

<multi-signature>
In P2PKH Multisig Transactions, what is the address?
user18688
# In P2PKH Multisig Transactions, what is the address?

(Asked by: username_0 on 2014-07-30)

In P2SH transactions, the address is the hash of the redeemScript. What is it for P2PKH transactions?

**Tags:** multi-signature


---

## 1 answers

### Answer by username_1 on 2014-07-30. Score: 2

There are no "addresses" in protocol. There are only "output scripts". The address is only human-readable representation of script which matches the "output script".

The output script for bare multisig transaction is [m] + [hash1] + [hash2] + ... + [hashN] + [n]

And all of these parts are significant. There is no "classic" representation of such address yet.

bc.i uses the form of **(Escrow X of X1 X2 X3)** (where Xn is standard p2pkh address) but you may use your own.

> **Comments:**
> **username_0**: So bare multisig transactions do not have "addresses"?  

---

