Hmm, those higher ranks are pretty expensive at today's prices...
That was my first thought as I started reading this post! It would be nice if the donation requirements were lowered. |
|
|
|
Sure, I can help you, just pm me with the details Edit - here is some instructions / tips for a cold wallet A plain cold wallet is actually fairly easy create, you just go to the bitcoin directory * and remove your wallet.dat. This file holds the private keys which allow you to access your bitcoins. It would be best to encrypt the wallet and store it in multiple places like on flash drives, CD's, etc. 7-zip is a very useful encryption tool which can be found here: http://www.7-zip.org/. If your not sure you trust 7-zip check out the wiki: https://en.wikipedia.org/wiki/7-ZipI would suggest looking at Armory for cold wallet storage with more safety and features. You can download it here: https://bitcoinarmory.com/. * Windows: C\Users\your-user-name\AppData\Roaming\Bitcoin Mac: Users/your-user-name/Library/Application Support/Bitcoin Linux: ~Home/.Bitcoin Hope this is what your looking for, BookLover |
|
|
|
|
Could you provide screenshots of guiminer's main page and the miner's settings page?
|
|
|
|
|
Could you be more specific in your question?
When a miner finds a block he is currently awarded 25BTC + fees. The block reward is hard coded to half approximately every four years and will eventually reach zero.
|
|
|
|
|
Something is wrong if you are still getting shares. Did you add rpcallowip=*, rpcuser=your_user_name, and rpcpassword=your_password to bitcoin.conf?
If you mining on the computer with the bitcoin server then the ip address and port should be 127.0.0.1 and 8332 respectively. If I remember correctly.
*IP address of your miner, assuming you mine on a separate computer from your server.
Hope this helps,
BookLover
|
|
|
|
|
Whatever way you find easiest. Possibilities are endless and just a search away.
It depends on so many factors that if someone gives you an answer without a lot of situational conditions he/she is just trying to up his/her post count.
|
|
|
|
Yes it is possible, but 2^256 is about 1.157920892 * 10^77 or a 1 in 115,792,089,200,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000 chance of it happening.  It is quite a bit more likely for you and all your family to die by meteorite. So moral of the story, buy meteorite insurance before worrying about address collisions.  Probability of death by meteorite found at :http://blogs.discovermagazine.com/badastronomy/2008/10/13/death-by-meteorite/#.UWhFucjLcTs it is 1 in 700,000 according to the site. P.S. Encrypting your wallet does nothing to prevent address collisions. |
|
|
|
|
Assuming you mean WINDOWS 7 you:
1) Create a shortcut for bitcoin-qt on your desktop.
2) Right-click the shortcut and select properties.
3) In the field labeled Target type -rescan on the end.
P.S. default is "C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" so the target field would end up looking like
"C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -rescan.
|
|
|
|
|
You would probably get more help if you moved this to "mining support".
|
|
|
|
|
What OS are you running? It is different for each one.
|
|
|
|
You can speed up Tor and reduce the time it takes the bitcoin client to connect by adding a list of fast exit nodes to the torrc file and the command "strictnodes 1". You can also put several "addnode" commands with ip addresses from http://blockchain.info/ip-log in your bitcoin.conf file. The second option is easier. here is example format for the addnode commands in bitcoin.conf: addnode=176.248.161.217
addnode=24.49.122.169
addnode=77.234.142.92
addnode=72.135.116.119
addnode=160.36.11.83 |
|
|
|
|
I don't get why everyone seems to have so much trouble with this. I sent less than 0.5 BTC with no fee and it confirmed on the next block. I guess "aged" wallets without a lot of dust transactions have a lot higher priority and don't need a fee.
|
|
|
|
It is possible your hard drive is dieing.  Maybe someone will come along with a more positive solution. |
|
|
|
|
try rescanning "-rescan".
|
|
|
|
The limit will be raised, of course. But why now OR in years? What about "in some months"?
0 < X < infinity. So it can be less than one year. Will change poll to reflect that. |
|
|
|
I state, "From what I've read", "I wanted to see what the common thought was", and "Please post your thoughts". And then get accused of spreading FUD?   Also, stating it is a bug fix is a) objective, and b) does not change the fact that with the 0.8 clients there eventually WILL be a hard fork. Not that this is necessarily bad, but there still will be a hard fork. |
|
|
|
To be clear: the 'donor' was the EFF, and their only request was that the Bitcoins be given back to the bitcoin community. If you like, think of it as a bulk payment of transaction fees that the faucet would have paid if it had been operating over the last year instead of closed (due to lack of time for me to fight the scammers).
Because it sent tiny transaction amounts, it paid almost as much in fees as it gave out...
Who is EFF? |
|
|
|
After talking with a few groups of people, I decided a good use of Bitcoin Faucet funds would be compensating miners who had blocks that were orphaned in last week's Bit Chain Fork.
This is a one-time thing-- don't expect orphaned blocks in the future to be compensated! It is just a coincidence that I haven't had time to fix the Faucet, and have a bunch of coins waiting to be given away.
Transaction id paying the to the addresses in the coinbases of the orphaned blocks: c931f1aa9f0d211dca085342ec472e77b538b55980a2c7b0ff9fab9a20a9acd2
This is wrong.  Funds not donated for this purpose were used without the permission of the donators. Return the coins. |
|
|
|
|
Show Posts
