Maybe it'll magically work again tomorrow? I was even suspecting some http-related library was automatically updated by Windows. Or some updated antivirus software... |
|
|
|
|
I got some user reports about this too.
At my end it looks just like poclbm suddenly stops submitting any shares.
Very sad to hear, poclbm was the best miner ever...
|
|
|
|
I can confirm that mine GUIMiner isnt working either. Getting tons of:
2012-02-04 22:07:01: Listener for "PH1": pit.deepbit.net:8332 04/02/2012 22:07:01, Unexpected error: Can you try any other miner like Phoenix or cgminer and tell us if it's working or not ? |
|
|
|
* My miners can mine to an address that is offline. My coins are secure. Why can't you do the same with any other pool ? |
|
|
|
Thanks. So it seems that this problem is somehow specific to poclbm. And it's the old version that was working before ? I can confirm this. Also I have poclbm miners that are currently working, but once you stop them they will no longer work upon re-start. I just checked other forum threads and noticed same problem reported by users from at least 3 or more pools, so it may be somehow caused by poclbm itself. That's very strange because it was the best miner ever. My logs show that those workers just stop submitting any shares, don't see any reason yet. |
|
|
|
That's right, if you have the Telnet Client turned on in windows features. Unfortunately, 90% of the people out there don't even know what Telnet is so they don't. Oh, may be that's how it works in those new versions of Windows. Never tried it. Phoenix works using the GUIMiner, the 'default' miner on GUIminer gives that error, however on a 1000mhz 6870 Phoenix only hashes at 280Mhash/s with flags, thats a pretty big fall in performance. Thanks. So it seems that this problem is somehow specific to poclbm. And it's the old version that was working before ? |
|
|
|
But this would never work:
"open your windows command line and enter
telnet pit.deepbit.net 8332" Always worked for me. I even checked it right now. |
|
|
|
I installed telnet client and it connects and shows an empty screen. If you don't see any errors then it means that connection is fine. Now it would be nice if you can try any other mining software like phoenix or cgminer. |
|
|
|
Try to check the connectivity with specific port: open your windows command line and enter
telnet pit.deepbit.net 8332
Then look if it shows some errors or just connects and shows empty screen. You cannot ping a port from a Windows command line but if you have a telnet client you should be able to telnet to it. I was talking about launching windows telnet client from command line, not pinging. |
|
|
|
Btw, one thing that made me go WTF when looking at interior pics of copacobana a few years ago... a single massive AC->1.2V converter for vccint and really heavy cables + busbars to route it around... Why they don't need any heatsinks on their FPGAs ? |
|
|
|
1. ping goes through with 100ms results no packet loss Try to check the connectivity with specific port: open your windows command line and enter telnet pit.deepbit.net 8332Then look if it shows some errors or just connects and shows empty screen. |
|
|
|
This possibility exists even today of course, but miners seem a lot more likely to organize and
attack right after (or right before) the mainstream network kicks them in the nuts
by halving the reward.
Maybe we will see a fork of BItcoin, which keeps the block reward at 50BTC, with a very high % I think that altcoins won't get any considerable chance to take over. Keeping reward at 50BTC per block is bad. Also, reward halving can work as self-fullfilling prophecy: people will expect price to rise and may stop selling BTC before the halving, causing price to rise. |
|
|
|
Been mining for awhile and i started to notice a fall-off in payment randomly, instead of 0.013 payouts it went to 0.004 or lower, i went to check it out and noticed some of my miners are displaying "Unexpected error" rather than getting work, now all of my rigs (8 rigs) are showing this message, deepbit down or? not understanding why the sudden change when the site shows normal Ghash. I received some user reports (~4 at this moment) about similar error message from their miner, working on DeepBit and at least one other pool. Since I don't see any considerable loss of total pool's hashrate, I can guess than it may be caused by some connectivity problem or software problem. Surprisingly, it started at the same time. 1. Check your connectivity by pinging pit.deepbit.net 2. Check if you have any antivirus software running, and WHEN it was updated for the last time. Did this time match ? 3. Try mining with some other miner - did the problem still persists or not ? |
|
|
|
Can you at least show the date and block id of the ones we found? "Your" block is shown in bold font at the stats page. I guess it was more than 5 days ago so it doesn't show on the stats pages available. Must have been from my first 6BTC then before I switched. Stats are available for ALL our blocks, you just have to request the page for some specific time. But yes, it's not as easy as just clicking the link :) |
|
|
|
Can you at least show the date and block id of the ones we found? "Your" block is shown in bold font at the stats page. And for your other questions I'll need more time to answer. |
|
|
|
|
Also I would like to say that at least partially all this mess is caused by the opcodes that Satoshi disabled more than a year ago.
I think that multisigs with short addresses can't be implemented without P2SH because OP_CAT op is disabled. May be.
|
|
|
|
Power/cooling to handle up to 5W per FPGA Not enough. Full-speed mining would require more than 8W per FPGA. Also, it's at least 3 times more expensive than currently available Spartan-6 mining solutions. |
|
|
|
-Let's say that in theory, I have a motherboard with 8 USB ports and 4 PCI-Express slots. So, always in theory, I could plug 8 FGPA board and 4 GPU in that motherboard and they could all mine together, correct? You can use USB hubs and additional USB controllers too. |
|
|
|
What is the recommend number of gpus per worker on deepbit? I recommend using one worker per one mining core. This also makes monitoring easier. Directing more than 20 miners to single worker account will disable LP for this worker. |
|
|
|
As long as at least a small fraction of miners accept the no-fee transactions as well, even those transactions will eventually make it into the blockchain. i.e., miners can try to force fees, but that action won't have much of an effect on the total amount of fees being paid. The BTC generation reward will likely remain to be the primary incentive [edit: rather than transaction fee revenue] to miners for some time yet.
Well it depends on how many miners. For example: if 50% of network hashes your transaction your 1 confirm time is now 20 minutes and the magic 6 confirm is 2 hours. if 25% of network hashes your transaction your 1 confirm time is now 40 minutes and the magic 6 confirm is 4 hours. if 10% of network hashes your transaction your 1 confirm time is now 100 minutes and the magic 6 confirm is 10 hours. if 4% of network hashes your transaction your 1 confirm time is now 4 hours and the magic 6 confirm is one day. Something is wrong with your calculations. 6 confirms is 1 confirm + 50 minutes on average. |
|
|
|
|
Show Posts
