Minor bug: Date of files on windows 64 bit version says 2013 year. Otherwise, it works.
Did you download the correct file? Mine shows
Code:
Freitag, 13. Februar 2015 18:38:10
in the signature.
Topic: Bitcoin Core 0.10.0 has been released - page 3. (Read 27238 times)
Did you download the correct file? Mine shows
in the signature.
Minor bug: Date of files on windows 64 bit version says 2013 year. Otherwise, it works.
I am currently using version v0.8.6-beta is there a reason for me to upgrade to version 0.10.0? I am a little afraid that my coins may be in danger in case I fail to do it right....
Simply backup your wallet.dat file to a safe location first (which you should always do before upgrading). Your coins will be "recoverable", should anything go amiss.
Every time you add a new address to your wallet you should back it up.
Thanks man, Ill install right now. 
today i launched core 0.1, and it stay there stuck at 100%, a bug?
try to rebuild the whole thing...
That is why I am afraid to patch it from my 0.8.6-beta version. While my current wallet can be slow as snail and took hour to start at least I know it will start. Stories like that just worries me more. try to rebuild the whole thing...
today i launched core 0.1, and it stay there stuck at 100%, a bug?
try to rebuild the whole thing...
try to rebuild the whole thing...
Currently doing the reindex thing...seems like it is resyncing the whole blockchain.
Thx for the soggestion.
Will let you know when it will end.
Thx for the soggestion.
Will let you know when it will end.
Use the command line -reindex on the shortcut of bitcoin core (and then, after the first lauch, delete the command line).
https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
Bitcoin core will be examinate the blockchain construction ... and resume the download.
At the worst, it re-download all the blockchain.
https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
Bitcoin core will be examinate the blockchain construction ... and resume the download.
At the worst, it re-download all the blockchain.
Not sure on how to do that?
Be aware I'm running it on windows 7
For Windows 7 in order to start bitcoin core with an additional command first close bitcoin core. Once its shut down completly, open "run" (Win + R) and enter (edit the path if you installed elsewhere):
Code:
c:\Program Files\Bitcoin\bitcoin-qt.exe -reindex
once you hit "ok" Windows will launch bitcoin core with the additional parameter(s). In the case of reindex it will take a few hours (depending on your CPU speed) to reindex the blockchain that is allready known. I would check the logs first (see below).
I did the steps you suggested even if, for what I know, such a move doesnt make any sense on windows.
Situation is still the same.
Noticed I only have outcoming connection and no incomig ones - number of connections 8 (0 incoming/8 exiting).
A couple of peers I'm connected to use 0.10.0, the other 6 have older version, abd they know blocks than me
Situation is still the same.
Noticed I only have outcoming connection and no incomig ones - number of connections 8 (0 incoming/8 exiting).
A couple of peers I'm connected to use 0.10.0, the other 6 have older version, abd they know blocks than me
This does not matter. As long as you have a connection to other nodes and they have blocks you dont you should be able to sync. You might find a reason for the error in the log files. You can find them if you enter
Code:
%APPDATA%/Bitcoin
in the run window and hit ok. It should open an explorer window showing the folder that contains your wallet.dat and other files. Among those files is the debug.log. See if it contains any clues or post the entries for e.g. today.
I am currently using version v0.8.6-beta is there a reason for me to upgrade to version 0.10.0? I am a little afraid that my coins may be in danger in case I fail to do it right....
Simply backup your wallet.dat file to a safe location first (which you should always do before upgrading). Your coins will be "recoverable", should anything go amiss.
Make a back up at least once a month or so I do and it is good practice to do too and make sure you have plenty of backups and make sure their password protected too and not just a wallet.dat that can be put back on. Just make sure to remember your password to it tho. No need to do a back up every time you receive or spend. Once a month or so is fine
I need to backup my wallet.dat file every time amount of my coins is changed? Or it is just some universal id of my wallet?
With bitcoin-qt, wallet.dat contains keys for all addresses that have been used already, plus 100 keys for addresses that have not been used yet.
So you really need to make a new backup only after about 100 new addresses have been used. Note that whenever you spend a bit, a new address is being used to receive the "change", so you need to count outgoing transactions, too. Of course, you should do backups much more frequently, but you don't need to back up your wallet after each transaction.
Hierarchical deterministic wallets (see https://en.bitcoin.it/wiki/Deterministic_wallet) compute all addresses from a single 128-bit seed which is normally represented as 12 common english words. For this kind of wallet, backing up the seed (which you can simply write down on a piece of paper) is all that you need.
Onkel Paul
I am currently using version v0.8.6-beta is there a reason for me to upgrade to version 0.10.0? I am a little afraid that my coins may be in danger in case I fail to do it right....
Simply backup your wallet.dat file to a safe location first (which you should always do before upgrading). Your coins will be "recoverable", should anything go amiss.
I am currently using version v0.8.6-beta is there a reason for me to upgrade to version 0.10.0?
Yes.
But if you experiment crash or other instability (if you run bitcoin core 24h/24) ... stay at the 0.9.1 instead.
I am currently using version v0.8.6-beta is there a reason for me to upgrade to version 0.10.0? I am a little afraid that my coins may be in danger in case I fail to do it right....
Simply backup your wallet.dat file to a safe location first (which you should always do before upgrading). Your coins will be "recoverable", should anything go amiss.
I am currently using version v0.8.6-beta is there a reason for me to upgrade to version 0.10.0? I am a little afraid that my coins may be in danger in case I fail to do it right....
Also tried this tool here
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
Forward incoming port 8333 on your router to the pc that is running core.
Any tip on how I may check if these are the reasons and how to forward port 8333 explicitly?
You've already checked, you are unreachable. The "how to" is up to you to know how to use your router/firewall.
Also tried this tool here
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
Is it possible that your router or firewall is set up to block incoming connections to port 8333?
(If using a router, you'd probably have to forward port 8333 explicitly unless bitcoin-qt is using UPnP and your router is set up to support it)
Onkel Paul
Any tip on how I may check if these are the reasons and how to forward port 8333 explicitly?
Also tried this tool here
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
Is it possible that your router or firewall is set up to block incoming connections to port 8333?
(If using a router, you'd probably have to forward port 8333 explicitly unless bitcoin-qt is using UPnP and your router is set up to support it)
Onkel Paul
I have questions.
#1 why would they want to disable their wallet?
#2 why put it in server mode?
#3 why limit to 2 connections instead of enforcing a single good connection to a fast node with -connect=IP?
#1 why would they want to disable their wallet?
#2 why put it in server mode?
#3 why limit to 2 connections instead of enforcing a single good connection to a fast node with -connect=IP?
1) Bitcoin core NODE feature
2) Bitcoin core SERVER (miner) feature
3) Because ... this is calling "experience" (i have tried 1,2,4,8,12,15,25,35,50 ... with 0.9.x, only 2 is the faster setting WHEN you are in SYNC mode).
Also tried this tool here
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
https://getaddr.bitnodes.io/
and it says I'm unreachable ....but I'm writing form the same pc where I'm running bitcoincore and with the same connection
Use the command line -reindex on the shortcut of bitcoin core (and then, after the first lauch, delete the command line).
https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
Bitcoin core will be examinate the blockchain construction ... and resume the download.
At the worst, it re-download all the blockchain.
https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
Bitcoin core will be examinate the blockchain construction ... and resume the download.
At the worst, it re-download all the blockchain.
Not sure on how to do that?
Be aware I'm running it on windows 7
I did the steps you suggested even if, for what I know, such a move doesnt make any sense on windows.
Situation is still the same.
Noticed I only have outcoming connection and no incomig ones - number of connections 8 (0 incoming/8 exiting).
A couple of peers I'm connected to use 0.10.0, the other 6 have older version, abd they know blocks than me
Jump to: