2013-10-16 05:14:30 +02:00
|
|
|
### SpendFrom ###
|
|
|
|
|
|
2013-01-05 02:05:56 +01:00
|
|
|
Use the raw transactions API to send coins received on a particular
|
|
|
|
|
address (or addresses).
|
|
|
|
|
|
2013-10-16 05:14:30 +02:00
|
|
|
Depends on `jsonrpc`
|
2013-01-05 02:05:56 +01:00
|
|
|
|
|
|
|
|
Usage:
|
|
|
|
|
|
2013-10-16 05:14:30 +02:00
|
|
|
spendfrom.py --from=FROMADDRESS1[,FROMADDRESS2] --to=TOADDRESS --amount=amount \
|
|
|
|
|
--fee=fee --datadir=/path/to/.bitcoin --testnet --dry_run
|
2013-01-05 02:05:56 +01:00
|
|
|
|
|
|
|
|
With no arguments, outputs a list of amounts associated with addresses.
|
|
|
|
|
|
2013-10-16 05:14:30 +02:00
|
|
|
With arguments, sends coins received by the `FROMADDRESS` addresses to the `TOADDRESS`.
|
2013-01-05 02:05:56 +01:00
|
|
|
|
|
|
|
|
You may explictly specify how much fee to pay (a fee more than 1% of the amount
|
|
|
|
|
will fail, though, to prevent bitcoin-losing accidents). Spendfrom may fail if
|
|
|
|
|
it thinks the transaction would never be confirmed (if the amount being sent is
|
|
|
|
|
too small, or if the transaction is too many bytes for the fee).
|
|
|
|
|
|
|
|
|
|
If a change output needs to be created, the change will be sent to the last
|
2013-10-16 05:14:30 +02:00
|
|
|
`FROMADDRESS` (if you specify just one `FROMADDRESS`, change will go back to it).
|
2013-01-05 02:05:56 +01:00
|
|
|
|
2013-10-16 05:14:30 +02:00
|
|
|
If `--datadir` is not specified, the default datadir is used.
|
2013-01-05 02:05:56 +01:00
|
|
|
|
2013-10-16 05:14:30 +02:00
|
|
|
The `--dry_run` option will just create and sign the the transaction and print
|
2013-01-05 02:05:56 +01:00
|
|
|
the transaction data (as hexadecimal), instead of broadcasting it.
|
|
|
|
|
|
|
|
|
|
If the transaction is created and broadcast successfully, a transaction id
|
|
|
|
|
is printed.
|
|
|
|
|
|
|
|
|
|
If this was a tool for end-users and not programmers, it would have much friendlier
|
|
|
|
|
error-handling.
|
