just updated with your steps
everything went fine!!
welldone!
Topic: Bitcoin-Qt / bitcoind version 0.8.6 released - page 6. (Read 34147 times)
thank you !
just updated with your steps
everything went fine!!
welldone!
just updated with your steps
everything went fine!!
welldone!
thanks to all!
bitcoind seems to be running fine on rk3188 ARM with latest p2pool, compilation failed with Fedora 19x64,will try later.
great work !
bitcoind seems to be running fine on rk3188 ARM with latest p2pool, compilation failed with Fedora 19x64,will try later.
great work !
Never. The Bitcoin devs specifically asked package managers not to.
Correct. It would be great to have the latest version in the package repositories but that's not how it works. Due to stable release policies and such they never keep it up to date.Use the PPA, at least we have that under control ourselves. https://launchpad.net/~bitcoin/+archive/bitcoin
When will come to the Ubuntu repository ?
Never. The Bitcoin devs specifically asked package managers not to.
but to go from ~160,000 (where it started) to ~274,000 (where we are now) took 24hours using >700% CPU on an 8 core i7 (Ivy Bridge). Not sure if this is normal behaviour/speed as normally I sync from the network most of the blocks...? I woudl appreciate if anyone would like to comment on this time taken...
This is why a new checkpoint would have been nice with this release, full transaction signatures are only verified for transactions in blocks after the checkpoint. I would think that is an unusual amount of CPU time though. 
I've looked around and can't find an answer regarding transaction fees paid by qt client. It seems like sometimes it asks for a trnasaction fee and sometimes it doesn't, and sometimes it says it's going to be one fee and then it's less when I confirm I want to do it. Finally I have heard you can do slower transactions for less fee but I can't find how to do this. Thanks
This may not be entirely accurate for this latest release of Bitcoin-Qt (as it only just came out!) but will explain fees pretty nicely for ya!
http://bitcoinfees.com/
So I downloaded this for use with OSX 10.9.
I added the app to the Applications folder after verifying the sig. As a shortcut, I copied accross the 'blocks' and 'chainstate' folders from a VM I had running bitcoind on Ubuntu 13.04.
I then opened the Bitcoin-Qt 0.8.6, which 'hung' at the "Opening wallet" splashscreen, for about 24 hours. Luckily I could see in the console debug.log that it was just verifying the blocks, but to go from ~160,000 (where it started) to ~274,000 (where we are now) took 24hours using >700% CPU on an 8 core i7 (Ivy Bridge). Not sure if this is normal behaviour/speed as normally I sync from the network most of the blocks...? I woudl appreciate if anyone would like to comment on this time taken...
It then proceeded to work as expected. I have closed and re-opened the app with no corruption, but have not yet powered the computer off (after safe shutdown) to see if I can then re-open without levelDB corruption.
Will update when I do this, but so far, thanks for this release!
I added the app to the Applications folder after verifying the sig. As a shortcut, I copied accross the 'blocks' and 'chainstate' folders from a VM I had running bitcoind on Ubuntu 13.04.
I then opened the Bitcoin-Qt 0.8.6, which 'hung' at the "Opening wallet" splashscreen, for about 24 hours. Luckily I could see in the console debug.log that it was just verifying the blocks, but to go from ~160,000 (where it started) to ~274,000 (where we are now) took 24hours using >700% CPU on an 8 core i7 (Ivy Bridge). Not sure if this is normal behaviour/speed as normally I sync from the network most of the blocks...? I woudl appreciate if anyone would like to comment on this time taken...
It then proceeded to work as expected. I have closed and re-opened the app with no corruption, but have not yet powered the computer off (after safe shutdown) to see if I can then re-open without levelDB corruption.
Will update when I do this, but so far, thanks for this release!
I just want to thank all of you for helping me with these issues. I am very new to this and I feel like the posters here are very helpful! Keep it up!!!
When will come to the Ubuntu repository ?
What is the secret to validating the download with the signature?
First, you check that the downloaded file match the SHA-256 checksum in SHA256SUMS.ascCode:
shasum -a 256 bitcoin-0.8.6-linux.tar.gz
Then you check that SHA256SUMS.asc itself has not been tampered with
Code:
gpg --verify SHA256SUMS.asc
I've looked around and can't find an answer regarding transaction fees paid by qt client. It seems like sometimes it asks for a trnasaction fee and sometimes it doesn't, and sometimes it says it's going to be one fee and then it's less when I confirm I want to do it. Finally I have heard you can do slower transactions for less fee but I can't find how to do this. Thanks
What is the secret to validating the download with the signature? I am used to verifying files having a download file say file.tar.gz and then a file.tar.gz.asc and running:
Code:
gpg --verify file.tar.gz.asc
after importing the authors public key. However with bitcoin-qt the signature file SHA256SUMS.asc seems to have signature data for all the different versions of bitcoin-qt. When I import Gavin Andresen's public key and run: Code:
gpg --verify SHA256SUMS.asc
I get "Good signature" no matter what. For instance if I completely delete bitcoin-0.8.6-linux.tar.gz I still get "Good signature" if I create a blank file called bitcoin-0.8.6-linux.tar.gz I still get "Good signature". It's as if it isn't actually verifying against the bitcoin-0.8.6-linux.tar.gz file. What am I doing wrong?
Yay I can finally combine my smaller amounts of BTC!
Is there any chance for future releases that the upload bandwidth used by bitcoind could have a throttle option?
There is a Linux script in contrib/qos that allows throttling the outgoing bandwidth for connections on the Bitcoin network.For other operating systems, there are likely similar ways to throttle certain applications/ports.
bitcoin y u no checkpoint??
>getblockcountsincecheckpoint
24258
>getblockcountsincecheckpoint
24258
Is there any chance for future releases that the upload bandwidth used by bitcoind could have a throttle option?
I don't have one of these new fangled VDSL or Cable connections, I have a 8mbit ADSL connection with a staggering 256k upstream. It gives me an upload speed of 38kb/s. Bitcoin-qt sucks up all of that bandwidth which makes even browsing webpages extremely slow and painful, sometimes impossible. It would be nice if there was an option (other than 'exit') so that bitcoin-qt couldn't hijack my internet connection.
I don't have one of these new fangled VDSL or Cable connections, I have a 8mbit ADSL connection with a staggering 256k upstream. It gives me an upload speed of 38kb/s. Bitcoin-qt sucks up all of that bandwidth which makes even browsing webpages extremely slow and painful, sometimes impossible. It would be nice if there was an option (other than 'exit') so that bitcoin-qt couldn't hijack my internet connection.
Electrum was made for you. You can also limit the connections from a long time ago.
Version 0.8.6 installed (over 0.8.5) succesfully in OSX 10.8.5 (Hackintosh) with an encrypted wallet. All ok. Thanks!
When you update the client do your bitcoins on the client stay intact?
Yes. But as always, backup your wallet.dat regularly to make sure a freak accident doesn't lose your coins.Edit: Looks like it is a subkey - https://github.com/bitcoin/bitcoin.org/pull/279
I would kindly suggest the release notes be edited to document this change as both differences happening with no warning is a bit scary.
I've added a note to the forum post.I would kindly suggest the release notes be edited to document this change as both differences happening with no warning is a bit scary.
When you update the client do your bitcoins on the client stay intact?
Bah, I forgot to code-sign the Windows .exe. Expect an updated .exe and SHASUMS soon.
Thanks Gavin! Jump to: