search

novitski / bitcoinj

Automatically exported from code.google.com/p/bitcoinj
Apache License 2.0
0 stars 0 forks source link

Wallet-Tool multi transactions #273

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Sending multiple payments at once does not appear to work, there is only one tx 
hash output regardless how many --output option I give.

The example given in the help screen is senseless, it talks about multiple 
--output options but then the example only has one. So what's the example 
wanting to tell me?

Its not clear how the fee applies to multiple transactions, and how can I apply 
different fees on each tx?

Also, it would be good if I could just add a pending tx to the wallet to be 
sent on next connect. Isn't that what --waitfor would be good for (for example 
--waitfor=TX_SENT|TX_CONFIRMED)? Because otherwise if I send 100 tx in a row I 
get blacklisted by the IRC server.

Original issue reported on code.google.com by andreas....@gmail.com on 11 Jan 2013 at 9:12

GoogleCodeExporter commented 9 years ago 
Um, using multiple --output options adds multiple outputs to the created 
transaction, not creates multiple transactions. What did you expect it to do? I 
can improve the help text but it won't change the fundamental nature of what 
the option does.

I guess there could be an option to suppress upload to the network, though does 
it have any use case beyond spamming the network? Why not solve your IRC 
banning problem by just specifying --peers= and picking the peer you used last 
time.

Original comment by hearn@google.com on 11 Jan 2013 at 9:29

GoogleCodeExporter commented 9 years ago 
Ok then I misunderstood the --output option, sorry.

I'm trying to create hundreds of tx in my wallet to test scalability. What's 
the fastest way to do this?

Original comment by andreas....@gmail.com on 11 Jan 2013 at 9:52

GoogleCodeExporter commented 9 years ago 
You could write a quick one off program to do that.

Original comment by hearn@google.com on 11 Jan 2013 at 9:57

GoogleCodeExporter commented 9 years ago 
But that's exactly what wallet-tool is meant for, if you ask me. I think I'll 
just uncomment the sending code for now. But really, I think you should use 
--waitfor.

Original comment by andreas....@gmail.com on 11 Jan 2013 at 10:00

GoogleCodeExporter commented 9 years ago 
Testing wallet scalability is a bit of an unusual use case, don't you think?

Original comment by hearn@google.com on 11 Jan 2013 at 10:01

GoogleCodeExporter commented 9 years ago 
Can you think of any usual use case you would use a CLI tool for? For 
everything usual, I'd use bitcoin-qt or Bitcoin Wallet.

Original comment by andreas....@gmail.com on 11 Jan 2013 at 10:06