Topic: Recent client build changes confirmation behavior? (Read 874 times)
Yeah that's a great idea, i'll give it a shot. Thanks
Waiting for confirmations is slowing development. I'm working on testnet for development, so I'm not worried about double spends.
You might want to set up a testnet-in-a-box environment, so you can pretty easily create blocks yourself to get transactions confirmed quickly: https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/
until the transactions have a bunch of confirmations.
1 confirmation is needed to respend your recevied coins. 6 confirms are recommended.
Hey,
I'm currently working on a basic bitcoin web app. I recently switched over to a self build of the bitcoin client to try and use sendtomany. However, it seems that the new compilation won't list coins to the balance or allow spending until the transactions have a bunch of confirmations. Is there any way I can get the old behavior where I could send coins out again almost immediately? Waiting for confirmations is slowing development. I'm working on testnet for development, so I'm not worried about double spends.
Thanks for any help,
Greg
I'm currently working on a basic bitcoin web app. I recently switched over to a self build of the bitcoin client to try and use sendtomany. However, it seems that the new compilation won't list coins to the balance or allow spending until the transactions have a bunch of confirmations. Is there any way I can get the old behavior where I could send coins out again almost immediately? Waiting for confirmations is slowing development. I'm working on testnet for development, so I'm not worried about double spends.
Thanks for any help,
Greg
Jump to: