Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I'm getting a "no block source available" message.
Oh! Ya that seemed to have been accepted. I tried restarting the client but got the same "no block source available" message. Should I be editing one of the files inside the protoshares folder instead?
I would very much support BTC-e
I'm not entirely sure how to do that. I tried entering variations of the code into the Console but always came up with "Method not found." Any idea what I'm doing wrong?
PTSPool already down.....
protoshares-qt.exe -addnode=cryptoseed.cloudapp.netor to protoshares.conf, example:addnode=cryptoseed.cloudapp.netprotoshares-qt.exe -connect=cryptoseed.cloudapp.net:80
I have done your command and will wait. For now it is still doing the No block thing but hopefully it will change after a while. Will let it go for the night. Thanks for the reply.
I have done your command and will wait. For now it is still doing the No block thing but hopefully it will change after a while. Will let it go for the night. Thanks for the reply.
Difficulty adjusted from 0.00001526 to ... and stay same
Edit: Reward was dropped by 5%, 2016 block to next retarget
Only block rewards is retargeted. Difficulty will retarget in 2016 blocks.
@bytemaster: Do you plan to update the wallet and make re-target every 2016 as planed? Or we stay as is?
I am going to keep it as is, no need to introduce a fork and people don't seem to mind the faster block production.
Difficulty adjusted from 0.00001526 to ... and stay same
Edit: Reward was dropped by 5%, 2016 block to next retarget
Only block rewards is retargeted. Difficulty will retarget in 2016 blocks.
@bytemaster: Can you modify your miner for support solo mining with a wallet? It's gives big advantages to the network.
Eventually... but at the rate difficulty is going up solo will not be a happening thing even with my faster miner.
Fixed the 1000 node limit, currently sitting at 1130 and counting...
10% CPU usage... we are good to go.
