I had seen a 21 million transaction in a unconfirmed state a while back. It soon disappeared, though.
Impossible. Perhaps 21 million base units, but not bitcoins. 
Topic: Cannot send unconfirmed coins from rpc. (Read 1537 times)
The RPC and GUI won't let you spend 0-confirmation transactions unless they are 'change' outputs from yourself.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, includingcounting your chickens before they've hatched spending unconfirmed-from-somewhere-else inputs.
I'll be looking out for short-lived 10 million Bitcoin transactions on blockchain.info! If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, including
The RPC and GUI won't let you spend 0-confirmation transactions unless they are 'change' outputs from yourself.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, includingcounting your chickens before they've hatched spending unconfirmed-from-somewhere-else inputs.
I'll be looking out for short-lived 10 million Bitcoin transactions on blockchain.info! If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, including
The RPC and GUI won't let you spend 0-confirmation transactions unless they are 'change' outputs from yourself.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, includingcounting your chickens before they've hatched spending unconfirmed-from-somewhere-else inputs.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, including
I'll be looking out for short-lived 10 million Bitcoin transactions on blockchain.info!
The RPC and GUI won't let you spend 0-confirmation transactions unless they are 'change' outputs from yourself.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, includingcounting your chickens before they've hatched spending unconfirmed-from-somewhere-else inputs.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, including
Thanks. That works for me, the 20BTC transaction was just an example I could post quickly, I'm really writing a satoshidice bot, and I'd like to keep it's balance very low...
I've never noticed that it didn't allow it before, I use coin control and send to myself fairly often, I'm guessing those transactions are included as "change"
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, including counting your chickens before they've hatched spending unconfirmed-from-somewhere-else inputs.
...there is also Brainwallet's transaction composer. Very handy, and I think it'll do unconfirmed transactions just fine! 
The RPC and GUI won't let you spend 0-confirmation transactions unless they are 'change' outputs from yourself.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, includingcounting your chickens before they've hatched spending unconfirmed-from-somewhere-else inputs.
If you REALLY want to shoot yourself in the foot, I've got a pull request for the 0.7 release that adds 'raw transaction' RPC commands that will let you do all sorts of dangerous things, including
0 confirm coins don't exist they aren't included in a block yet. Theres no header to include. You don't know what block they will be included in.
What are you talking about?! You reference previous transactions, not blocks or block headers.
0 confirm coins don't exist they aren't included in a block yet. Theres no header to include. You don't know what block they will be included in.
I cannot seem to get bitcoind to allow me to send 0-confirm coins. Is this by design, or a bug? I'm using the latest version from the ubuntu ppa.
I've tried both sendfrom and sendmany.
sendfrom [minconf=1] [comment] [comment-to]
sendmany {address:amount,...} [minconf=1] [comment]
root@bt:~# bitcoind getbalance
2.8245
root@bt:~# bitcoind getbalance "" 0
23.7164
root@bt:~# bitcoind sendfrom "" 1Meb94yEgFWN8SQ5JYVNTXU12qBa7a1eiY 20 0
error: {"code":-4,"message":"Insufficient funds"}
I've tried both sendfrom and sendmany.
sendfrom
sendmany
root@bt:~# bitcoind getbalance
2.8245
root@bt:~# bitcoind getbalance "" 0
23.7164
root@bt:~# bitcoind sendfrom "" 1Meb94yEgFWN8SQ5JYVNTXU12qBa7a1eiY 20 0
error: {"code":-4,"message":"Insufficient funds"}
Jump to: