<p>This is a limitation on the interface used for send many. The <code>address,amount</code> list is a dictionary internally within Bitcoin Core, and cannot have duplicate keys. As many other projects are forks of Bitcoin Core, the limitation applies to them as well.</p>

<p>You can work around this by constructing a transaction manually or with a library that doesn't not use the RPC interface, nothing at the actual protocol level prevents this.</p>

CC BY-SA 4.0
2019-10-06T07:05:40.640Z
2019-10-06T07:05:40.640Z
Raghav Sood
<p>The use of sendmany in a PoS coin is an obvious source for preparing stake inputs, however it historically has been prevented to send  to duplicate addresses in one transaction with such an error as "Invalid parameter, duplicated address:"</p>

<p>It seems like a reasonable issue in BTC, but are there any good reasons to prevent this?</p>

<transactions><proof-of-stake><address-reuse>
Any good reason to prevent duplicated address in send transaction for Pos coin?
watermelon
# Any good reason to prevent duplicated address in send transaction for Pos coin?

(Asked by: username_0 on 2019-10-06)

The use of sendmany in a PoS coin is an obvious source for preparing stake inputs, however it historically has been prevented to send to duplicate addresses in one transaction with such an error as "Invalid parameter, duplicated address:"

It seems like a reasonable issue in BTC, but are there any good reasons to prevent this?

**Tags:** transactions, proof-of-stake, address-reuse


---

## 1 answers

### Answer by username_1 on 2019-10-06. Score: 1

This is a limitation on the interface used for send many. The `address,amount` list is a dictionary internally within Bitcoin Core, and cannot have duplicate keys. As many other projects are forks of Bitcoin Core, the limitation applies to them as well.

You can work around this by constructing a transaction manually or with a library that doesn't not use the RPC interface, nothing at the actual protocol level prevents this.


---

