Topic: Bitcoin-Qt / bitcoind version 0.8.0 released - page 2. (Read 29419 times)
If you don't have the resources to run Bitcoin-Qt, consider moving to MultiBit or some other lighter weight wallet app.
Why does Bitcoin-qt hog 99% of CPU for WinXP, slow down and make itself unusable, when downloading the last 10000 blocks or so? I cannot afford to burn my cpu at 80+ degrees celsius for days for downloading the last gigs of blockchain - where would high cpu resources used anyway, isn't the client doing mainly just download and not processing tasks?
Sorry if a wrong thread, it's frustrating to be unable to use the client since versions from past year or so. I would like to say bad design, but of course won't do it here.
Sorry if a wrong thread, it's frustrating to be unable to use the client since versions from past year or so. I would like to say bad design, but of course won't do it here.
In Mac OSX 10.8.2, when I minimize the bitcoin wallet, it doesn't ever show up again, when I click the app in the dock also when I click show all windows it doesn't up. So this is probably a bug, that should be check out it has happened like 4 times to me.
This happens to me too. (tested on 3 different machines)
In Mac OSX 10.8.2, when I minimize the bitcoin wallet, it doesn't ever show up again, when I click the app in the dock also when I click show all windows it doesn't up. So this is probably a bug, that should be check out it has happened like 4 times to me.
Yep, I already reported that.
Sorry if this has already been covered, but I can't seem to get the transaction fee setting to "stick" after I close the client. It only works for as long as the client stays running, and if I shut it down and restart it again the transaction fee to send goes back to .00000000 BTC. Any ideas on this one?
Probably paytxfee=0.00 in the bitcoin.conf file.
Sorry if this has already been covered, but I can't seem to get the transaction fee setting to "stick" after I close the client. It only works for as long as the client stays running, and if I shut it down and restart it again the transaction fee to send goes back to .00000000 BTC. Any ideas on this one?
- snip -
Also it could be great if we are able to select the address that sent btc from.
The client just use all my available addresses!
blockchain.info grossly misrepresents how Bitcoin works in various ways.Also it could be great if we are able to select the address that sent btc from.
The client just use all my available addresses!
- snip -
Bitcoin does not have "from" addresses.
It could be great if we were able to select the outputs that were used as inputs. The client just seems to randomly select outputs.
Or should I stop the process in mid-stride (kill -stop ) and kill -cont it later?
I wouldn't do that, because if "something happens" this is equivalent to a crash. some pages before I did do some -9 kills and it corrupted my wallet and bitcoind didn't start any more. so, to be on the safe side, shut it down 
Is it safe to do a "bitcoind stop" in the middle of the upgrade? Will I lose any work already done?
Or should I stop the process in mid-stride (kill -stop) and kill -cont it later?
Or should I stop the process in mid-stride (kill -stop
I'd say both are safe.
During the upgrade if we want to pause it (e.g. to get some work done), what is the best way to do that? I'm running on Ubuntu 12.04.
E.g. I ran "bitcoind -daemon" (I wish I could leave that daemon running and have bitcoin-qt reference it....)
Is it safe to do a "bitcoind stop" in the middle of the upgrade? Will I lose any work already done?
Or should I stop the process in mid-stride (kill -stop) and kill -cont it later?
E.g. I ran "bitcoind -daemon" (I wish I could leave that daemon running and have bitcoin-qt reference it....)
Is it safe to do a "bitcoind stop" in the middle of the upgrade? Will I lose any work already done?
Or should I stop the process in mid-stride (kill -stop
Thank-you to all involved for your continued hard work and development.
Long-time user, here. Just launched 0.8 for the first time. I have the setting made to connect through proxy only (Tor). The new client inherited that setting from previous installations. I FORGOT to launch Tor, but the blockchain is downloading anyway.
If I am not mistaken, this means it is connecting to the network, ignoring the proxy checked setting.
UPDATE: It stopped syncing at 26 days left. So maybe the bootstrapped portion of the block does not go through proxy?
The reindex comes off your hard drive (previous version's data). If I am not mistaken, this means it is connecting to the network, ignoring the proxy checked setting.
UPDATE: It stopped syncing at 26 days left. So maybe the bootstrapped portion of the block does not go through proxy?
Long-time user, here. Just launched 0.8 for the first time. I have the setting made to connect through proxy only (Tor). The new client inherited that setting from previous installations. I FORGOT to launch Tor, but the blockchain is downloading anyway.
If I am not mistaken, this means it is connecting to the network, ignoring the proxy checked setting.
UPDATE: It stopped syncing at 26 days left. So maybe the bootstrapped portion of the block does not go through proxy?
If I am not mistaken, this means it is connecting to the network, ignoring the proxy checked setting.
UPDATE: It stopped syncing at 26 days left. So maybe the bootstrapped portion of the block does not go through proxy?
can you remember the smell of paper tape?
I remember my Dad used to bring rolls of it home from work and we'd make Christmas decorations out of it. I remember starting to decode a tape one time, looking up the ASCII codes one by one and hoping to find official secrets or something. I gave up after "10 REM STAR TREK GAME" or some such.
LOL. Looks like you did.
can you remember the smell of paper tape?
I remember my Dad used to bring rolls of it home from work and we'd make Christmas decorations out of it. I remember starting to decode a tape one time, looking up the ASCII codes one by one and hoping to find official secrets or something. I gave up after "10 REM STAR TREK GAME" or some such.
thanks Luke junior :p
indeed no "fee" line exists in transaction details!
for one moment i was afraid that bitcoin network start using fees by its own
indeed no "fee" line exists in transaction details!
for one moment i was afraid that bitcoin network start using fees by its own
I send 20btc today from Bitcoin-Qt without selecting any fee but i saw in blockchain info that a fee of 0.01000022 has been issued!
is this a bug or something else? should i set a default fee? how low?
Also it could be great if we are able to select the address that sent btc from.
The client just use all my available addresses!
blockchain.info grossly misrepresents how Bitcoin works in various ways.is this a bug or something else? should i set a default fee? how low?
Also it could be great if we are able to select the address that sent btc from.
The client just use all my available addresses!
Please check your client to see the actual fee (double-click on the transaction on the Transactions page, if there is a fee it will show "Transaction fee: x BTC" - if it doesn't show this exact line, there was no fee paid).
Bitcoin does not have "from" addresses.
I send 20btc today from Bitcoin-Qt without selecting any fee but i saw in blockchain info that a fee of 0.01000022 has been issued!
is this a bug or something else? should i set a default fee? how low?
Also it could be great if we are able to select the address that sent btc from.
The client just use all my available addresses!
is this a bug or something else? should i set a default fee? how low?
Also it could be great if we are able to select the address that sent btc from.
The client just use all my available addresses!
For all the people interested in getting Bitcoin 0.8 into the newest version of Ubuntu - to be released in April - please mark this bug as affecting you: https://bugs.launchpad.net/ubuntu/+source/bitcoin/+bug/1130638
Jump to: