i actually want to see the .dat file. i went to the ling you sent and it told me to use this command find / -name wallet.dat -print 2>/dev/null i got the response bash: /dev/nul: Permission denied .....?........any ideas
Did you enter that command as root? Otherwise prepend "sudo".
|
|
|
It doesn't make a difference. Though some people will say it's a privacy concern.
Also, depending on the wallet you use, as soon as you spend from your "one" address, most wallets will create a new change address, so after a few tx your BTC will be "scattered" again.
|
|
|
Report the false positive to Bitdefender.
|
|
|
If you think it's bandwidth related you can speed it up using the torrent bootstrap.dat or using the latest release candidate 0.10.0. From my observation however it is normal for it to slow down the closer it gets to the latest block. Also remember it is validating the whole blockchain, so your VPS' hardware specs matter too.
|
|
|
What version?
Did you change anything in the default settings?
|
|
|
[...] once the next build comes out with db improvements, i'll try again.
Same for me. No special flag, I had it build the DB for some 60 hours or so. It's at 64% now. Going the last 4% of that took ~8 hours. Seems a 2012 model laptop with an i5-3317U and 6GB RAM is not enough for a regular installation?
|
|
|
Yesterday I saw over 100 cars on the road that I didn't recognize. I think it's safe to say that it was the same guy driving all of them and that his name is "Unknown". He must be very rich to have so many cars. Not sure if you refer to my posting. However, the 27 blocks from "Unknown" were mined by the company which is financing MBP, so I assume they are the same... not excluding, though, that I'm totally wrong. How do you know? Got an example block?
|
|
|
Perhaps you missed that 9.4.0 is now available on the ppa, fixing that issue.
|
|
|
Sorry, offtopic. Nope, I'm talking about regular consumer bank accounts. Both national and international wire transfers (within SEPA zone) are 100% free. [...]
Is a regular bank account at your bank also free?
|
|
|
Did a trade with somebody who uses the German version of Mycelium. Mine is in English. My trade history now shows "Sie haben den Betrag freigegeben." (You released the funds.) All the other Local Trader messages are in English.
|
|
|
That is your decision. bc.i had many problems over the last 6 months. They claim they were fixed and everything is fine, others claim there are still other bugs. Who do you believe?
Me personally, I want to be in control of the private keys 100%. At bc.i you are not, regardless what they say.
|
|
|
I just compiled bitcoin core on ubuntu, where exactly is my wallet.dat file that i would like to back up....i cant find it
You can back it up from within the program or find it here: https://en.bitcoin.it/wiki/Data_directory
|
|
|
[...] WARNING
Before reading this page, users should note that messing with ECDSA private keys is very dangerous and can result in losing bitcoins, even long after the import. It is recommended that outside of self-generated vanity addresses, users should never import (or export) private keys What does this mean? this is at the wiki. Some other user tried to explain it but I couldnt quite understand and didn't get any answers off anyone else. It means if you generate your own private keys you need to trust 100% your random source. A weak random number generator produces weak keys which may only be found about out much later on. Question number 2: I then came across this message: Because bitcoins can only be spent once, when they are spent using a private key, the private key becomes worthless. It is often possible, but inadvisable and insecure, to use the address implemented by the private key again, in which case the same private key would be reused. What does this mean? I've imported the private key just to verify....but I'm wondering if I can recieve bitcoins in the future and also send any transactions when I need to. I'm a little concerned about the warnings and want to reassure myself thanks for your patience. There's a privacy issue and a technical for some, but the main issue was with people spending from Bitcoin Core with imported private keys and then they deleted the wallet.dat file. The change from the spent transaction went to a address generated by Bitcoin Core and when that wallet.dat was deleted the change address and private key for it were lost. There's other solutions now, for example Mycelium offers a way around that and makes spending from private keys easy.
|
|
|
Which Bitcoin Core version are you using?
|
|
|
The process will take "long" regardless. The program validates the whole blockchain. This depends on your PC specs.
|
|
|
Why many guys seek extremely low temp just to raise the overclock potential, using even liquid nitrogen? [...]
How about this? Say an electronic part performs at best when it's at 60 degrees. An overclocker without Nitrogen would otherwise run it at 100, but the Nitrogen brings it back to 60. What you are trying is to run at 40 and expect better results. But the part is not in its preferred range, so the efficiency is less.
|
|
|
|