As discussed on the #bitcoin-dev IRC channel, enforcing unique addresses in sendmany is useful because it may prevent the user from accidentally paying somebody twice. If you really want to, it should be possible to include the same address multiple times using the rawtransaction commands, though.
Allow createrawtransaction to accept duplicate addresses #2366
pull zechiel wants to merge 1 commits into bitcoin:master from zechiel:master changing 1 files +1 −3-
zechiel commented at 1:48 AM on March 14, 2013: none
-
Allow createrawtransaction to accept duplicate addresses efba4ab3f3
-
BitcoinPullTester commented at 2:33 AM on March 14, 2013: none
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/efba4ab3f3a26c03f5253133a45e8025e2c447e2 for binaries and test log.
-
gavinandresen commented at 4:05 AM on March 14, 2013: contributor
You should just remove setAddress entirely.
NACK on doing it that way though, it violates the JSON-RPC standard: http://www.ietf.org/rfc/rfc4627.txt?number=4627
Section 2.2 : "...names within an object SHOULD be unique."
-
sipa commented at 9:06 PM on April 12, 2013: member
Closing until a JSON-compliant solution exists.
- sipa closed this on Apr 12, 2013
- ejose19 cross-referenced this on Sep 28, 2019 from issue Allow sending to duplicate address in bitcoin rpc by ejose19
- hloo cross-referenced this on May 14, 2020 from issue z_sendmany multiple output to the same address by Tomas-M
- sidhujag referenced this in commit d1a000e6d5 on Oct 28, 2020
- bitcoin locked this on Sep 8, 2021
