|
Try opening the console and typing "dumpprivkey 149ygujMrWdmvd6Q4Jcx6J3Gkb39mmehGH" (without the quotes). Don't post the output here but just use the command to make sure the private key for those coins is in your wallet. Let us know if the command suceeds or if you get an error.
|
|
|
|
|
Bitcoin Core is probably the most popular because it incorrectly assumed to be "the default wallet". The wallet that's best for you depends on what you want to use it for. I personally use both Bitcoin Core and Multibit. If your looking for an offline wallet Armory is a good place to start.
|
|
|
|
Get 2 (at least), preferably of different brands/types.
Even a very reliable brand may sometimes produce a lesser copy. You don't want to put all your eggs in one basket.
+1, was going to say the same thing  |
|
|
|
You using bitcoin-qt correct? Try launching it with the command line option -rescan. I think you may still have your coins. You may just be confused because of some under the hood functionality. There are two outputs in that transaction due to change: https://en.bitcoin.it/wiki/Change. Let me know what -rescan turns up. |
|
|
|
It can import private keys but not bitcoin-qt's wallet.dat. To import your wallet from bitcoin-qt to multibit you need to first export your private keys from bitcoin-qt using the dumprivkey command and then import those keys into multibit. |
|
|
|
If you are using 0.9 'standard' fees you are likely to have a bad time.
The devs unilaterally dropped fees by a factor of 10. Unless all the large miners agree, there are going to be a lot of slow confirmations over the next few weeks.
Could you explain in simple terms, what fee should we use to send 1 BTC if we want to see some confirmations within 30 minutes? I see this question come up all the time, maybe there should be a sticky announcement or something... Read the wiki: https://en.bitcoin.it/wiki/Transaction_fees. It does an excelent job of explaning transaction priority and how fees affect the priority. |
|
|
|
|
If you never created a passphrase you can just ignore the "type: walletpassphrase "your walletpassphrase" 600" and go strait to exporting your private keys using the dumpprivkey command.
|
|
|
|
|
Can you post the transaction id?
|
|
|
|
Unless you or someone else can access your old address your coins are gone.  |
|
|
|
|
Depending on you hard drive it could take longer than 48 hours, so don't panic if it takes awhile.
|
|
|
|
|
The blocks and chainstate folders and any files named block***.dat in the bitcoin directory. (the files, if you have them, are left over from the old blockchain format)
|
|
|
|
|
Have you tried using the standard port? (8332)
|
|
|
|
Wow, you waited 18 minutes before accusing the bitcoin community for not being helpful.  Just give it a little time, someone with experiance should be able to help (assuming he isn't driven away by your comment). I don't really know your situation (nor am I very proficent at networking), but I'd try installing Tor and routing bitcoind through it and see if it solves the problem. |
|
|
|
For your situations I can not say for sure one way or another, I can simply say that in majority of cases the main limitation is the hard drive speed I said main limitatoin, not only limitation. In the average computer the hard drive is the limiting factor, speed it up and you speed the sync speed. You can, of course, get into situations where your hard drive speed is not the limiting factor. (I haven't yet) |
|
|
|
|
I've never heard of anything like this. While it sounds cool I'm not sure how much it would really help the reindexing process as the main limitation is the hard drive speed. An upgrade to SSD or RAID array is the way to go if you want to increase your reindex and sync speed.
|
|
|
|
90% of my posts are on the technical support forum where I help others solve their problems. Apparently tipping is overated  (notice amount in address), but I keep doing it anyway. examples: Just install Tor with the default settings and then in bitcoin-qt go to settings, options, network and change the port to 9150. (make sure "Connect through SOCKS proxy" is selected and that the SOCKS version is 5)
P.S. I not sure if Tor is set to configure controlport automatically by default or not, but if the above doesn't work you can try going to the advanced tab in Tor and deselecting it.
Add the Bitcoin Ubuntu PPA repository in your Ubuntu sudo add-apt-repository ppa:bitcoin/bitcoin Update package lists Install bitcoin-qt sudo apt-get install bitcoin-qt Just copy and past the code into terminal and you should have the latest version of bitcoin-qt. If you prefer not to use a PPA you can download the latest linux client from here: http://bitcoin.org/en/download. Just decompress the .tgz file and you've got the latest version of bitcoin-qt. Hope the OP comes back to the thread to see this. I doubt he found the solution on his own. P.S. You can furthur validate my story by checking my post history. P.P.S. Address in sig. |
|
|
|
|
You can multiple instances of bitcoind if you use different data directories. Just create a shortcut for each of the instances you want to run and add -datadir=C:\"data_directory_for_that_instance" to the target line.
|
|
|
|
|
Then this is not your problem, you need to have performed those actions over 100 times combined for this to have been an issue.
You're using bitcoin-qt correct?
If so is your wallet synced?
|
|
|
|
|
1. The hoter you run your GPU's, the more stress they will be under and the sooner they will fail. That being said there is no one perfect temperature or temperature range. As you have seen most people (including me) prefer to run there GPU's at 75-80C.
2. Here's a few ways to lower your GPU temperature: put the computers in a cooler environment, add fans to increase air movment (you can also remove the case sides and add external fans), lower the GPU clock and voltage settings, and cgminer may have some options you can use.
|
|
|
|
|
Assuming the Mintcoin wallet qt interface is similar to bitcoin-qt's interface (this could be a completely wrong assumption), just open the receiving address tab and copy a receiving address from there. You should also be able to generate new receiving addresses there.
|
|
|
|
|
Show Posts
