Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sendmany attempt #187

Merged
merged 2 commits into from
Aug 17, 2013
Merged

sendmany attempt #187

merged 2 commits into from
Aug 17, 2013

Conversation

nelisky
Copy link
Contributor

@nelisky nelisky commented Apr 8, 2013

I needed to have sendmany like in bitcoin-qt, but with change address and fee control. Of course electrum is always my go-to client for custom tailored transactions without the perils of creating them by hand, so I took a stab at it.

I have not tested actually submitting the tx, but I reviewed a bunch of them from mksendmanytx and it looks very sane, as it should as the change is minimal.

I thought about piggybacking on payto/mktx, as the optional 'label' described in the help text does not seem to be processed anywhere, but I only did a quick search for it and didn't want to change the existing command expected behaviour.

A simple argument parsing change from mktx to allow passing multiple recipients
Just like mktx/payto, this is only submitting the tx created in mksendmanytx
@ghost ghost assigned ecdsa Jun 17, 2013
@Rui-Santos
Copy link

Will this be merged? Would love to have sendmany on Electrum also.
BTW, was looking at your code and didn't see the error detection for duplicate addresses on the outputs list. Not sure if it's a protocol or client only thing, but Bitcoin-qt fails when a sendmany transaction has more than one output to the same address.

ecdsa pushed a commit that referenced this pull request Aug 17, 2013
merging sendmany attempt in master
@ecdsa ecdsa merged commit 62cdb14 into spesmilo:master Aug 17, 2013
@ecdsa
Copy link
Member

ecdsa commented Aug 18, 2013

merged to 1.9 branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants