Had to read this post to see who would try and hire out 6 mh/s  . I think he probably means 6 gh/s that's more realistic with 12 7950s. |
|
|
|
Actually, since you were using Bitcoin-Qt, the change went to a brand new address never seen in the wallet before.
This isn't quite true, while the address has never been used by the wallet before it is in the wallet along with another 99 addresses in the keypool. (99 assumes you haven't manually changed the size of the keypool) |
|
|
|
|
You have to set it to port 9051 by going to Settings - Advanced and deselecting the checkbox labeled Configure ControlPort automatically, this should fix your problem.
|
|
|
|
Try typing cgminer -o http://binarycoins.eu:9333/ -u p -p 1 -I 7 in command prompt and see if it works without the extra settings. |
|
|
|
|
Assuming your using windows get Catalyst Conctrol Center (CCC).
|
|
|
|
|
Use Tor. You can even run your bitcoin client through it.
|
|
|
|
|
When you send a PM you have to check the box labeled "Save a copy in my outbox" in order to view sent PMs
|
|
|
|
|
If you close bitcoin-qt and cgminer stops hashing then you are solo mining.
|
|
|
|
Is there something wrong with this? http://testing_1:123@stratum.btcguild.com:3333/or this? http://testing_1:123@btcguild.com:3332/If I'm not inputting the pool info wrong then I have no clue as to why it isn't working.  I can access the internet so that isn't the issue. I don't know what stratum is so there may be something wrong there, but the second address should have worked if this was the case.EDIT: Figured out what stratum was and decided to try out cgminer on Linux Mint. |
|
|
|
|
try using the quantal distribution instead of nadia. Also, (don't know if this is necessary) get the ppa for the source code in addition to the binary.
|
|
|
|
What would be acceptable proof that I am Satoshi?
To prove your Satoshi, you don't tell people your Satoshi.  Jokes aside if you moved some coins which 'you' mined really early on, then that would be decent proof your satoshi. |
|
|
|
This does not account for aliens and other beings that are capable of manipulating the Universe, time to dump my coins.
USD and all other fiat fail to account for that as well. |
|
|
|
|
If you send smaller transactions to yourself you can combine the dust transactions and create larger inputs. This may not work if the dust inputs are to small.
|
|
|
|
As D&T advised keep several backups (naming according to date is not a bad idea at all) and also with any significant amounts you would be advised to use "cold storage".
Already covered. I even have them named by date. Thanks for all the info,  BookLover |
|
|
|
|
Wasn't that changed in version 0.8.0?
|
|
|
|
|
I was unclear in my previous post. I encrypted manually using 7-zip, not the built in encryption option of bitcoin-qt.
|
|
|
|
|
Let me make absolutely sure I understand correctly.
So if I encrypted a wallet with a keypool size of 100.
Copied the encrypted wallet and decrypted the copy.
Started bitcoin-qt with the copied wallet and the keypool=500 command.
Sent coins.
Deleted copied wallet.
Then my encrypted wallet still has the private keys to all my coins? (assuming it already had plenty of spare keys)
Thank you for you time and for promoting my sanity,
BookLover
|
|
|
|
|
If I put keypool=500 in bitcoin.conf, then are 500 new address created for the keypool? Or are the existing 100 preserved and 400 added to reach 500?
Questions and thoughts appreciated,
BookLover
|
|
|
|
You only need to transfer the blocks and chainstate folders between the bitcoin directories.  You missed the chainstate folder. |
|
|
|
If you're mining, don't use crossfire. |
|
|
|
|
Show Posts
