<p>This is a historical oddity.</p>

<p>In the past, Bitcoin Core would report the list of participating keys in a multisig addresses by listing the addresses for those keys. This was both confusing (addresses and keys are distinct things), but also unreliable, as the full public keys were not always knowm (when P2Sh was introduced). You can  safely assume you won't see multiple addresses in any output to an address created in modern times.</p>

CC BY-SA 4.0
2019-07-19T19:02:36.680Z
Do we have any transactions in the blockchain which has more than one address in the output?
Tailer
CC BY-SA 4.0
2019-07-19T19:15:52.827Z
Yes, all bare multisig outputs.
Pieter Wuille
CC BY-SA 4.0
2019-07-19T17:00:27.057Z
2019-07-19T17:00:27.057Z
Pieter Wuille
<p><a href="https://bitcoin.stackexchange.com/questions/11279/why-vout-addresses-in-getrawtransaction-is-a-table">this</a> answers why vout.scriptPubKey.addresses is an array,</p>

<p>then why the address in listunspent response is a String?</p>

<p>Do you know any transactions in the blockchain have multi addresses in the vout?</p>

<bitcoin-core><listunspent><getrawtransaction>
listunspent bitcoin core command returns the address as String while getrawtransaction addresses are array
Tailer
# listunspent bitcoin core command returns the address as String while getrawtransaction addresses are array

(Asked by: username_0 on 2019-07-18)

[this](https://bitcoin.stackexchange.com/questions/11279/why-vout-addresses-in-getrawtransaction-is-a-table) answers why vout.scriptPubKey.addresses is an array,

then why the address in listunspent response is a String?

Do you know any transactions in the blockchain have multi addresses in the vout?

**Tags:** bitcoin-core, listunspent, getrawtransaction


---

## 1 answers

### Answer by username_1 on 2019-07-19. Score: 1 | Accepted answer

This is a historical oddity.

In the past, Bitcoin Core would report the list of participating keys in a multisig addresses by listing the addresses for those keys. This was both confusing (addresses and keys are distinct things), but also unreliable, as the full public keys were not always knowm (when P2Sh was introduced). You can safely assume you won't see multiple addresses in any output to an address created in modern times.

> **Comments:**
> **username_0**: Do we have any transactions in the blockchain which has more than one address in the output?  
> **username_1**: Yes, all bare multisig outputs.  

---

