Topic: [9 TH] Bitparking Pool, DGM 0%,vardiff,stratum,Merge Mining - page 41. (Read 163893 times)
Looks like the site is down as well; "502 Bad Gateway"
Stratum isn't working correctly too:
Bitparking is pool 1
Bitparking is pool 1
This is not working for me either. I just tried.
Bitcoin withdraw failed with "Fatal error: Error fetching URL"
Daemon is down?
Yes, back up now.Daemon is down?
Is getwork down? My getworkers are not working 
Check the main page, the 0 MH/s rate directed at the getwork port indicates it is down.
You can try using stratum_proxy, though it is quite buggy for me. Not as efficient as connecting straight to the getwork port, but better than nothing. Theoretically, it ought to be MORE efficient I believe, but I get a lot of errors from the proxy.
Is getwork down? My getworkers are not working
getwork seems to have gone down again. I've switched back over to stratum-proxy for now.
Bitcoin withdraw failed with "Fatal error: Error fetching URL"
Daemon is down?
Yes, back up now. Daemon is down?
Bitcoin withdraw failed with "Fatal error: Error fetching URL"
Daemon is down?
Daemon is down?
What about TX fees? Are already paid out?
No, transactions fees are not yet paid out. 
What about TX fees? Are already paid out?
EDIT: Did you notice the last news on the page is 2013-02-14. All news after that are gone...
EDIT: Did you notice the last news on the page is 2013-02-14. All news after that are gone...
above your comment in the Bitminter vs. Eligius thread. Any explanation why the orphan rate is much higher than expected. There are 8 orphan out of 188 blocks since the DGM-switch. This equals 4.2% ophans, much more than normal! Now it matters, because you are not paying orphan blocks anymore. Taking your numbers, the effective Bitparking fee is 4,7%.
I've mentioned this before but not all those orphans were real orphans but were the result of the pool paying out on stale submissions that solved a block. I flagged them as orphans in the pool accounting system as it's the only way to note in the reserves that a payment was made but no income received. The bug causing this was fixed before the switch to the pool not paying for orphans.Since the switch there have been two orphan blocks, both genuine close races. The most recent one I think our block was submitted something like 10 seconds after the racing block - not much you can do about that.
After Bitminter and slush, Bitparking would get my vote. They don't pay tx fee rewards, but offer 3 merged mined altcoins.
Bitparking also pays for orphans. This is what the transaction fees go towards - keeping an orphan buffer. If the network has averaged 1% orphans in the last 12 months then the 1.5% fee at bitparking is really only 0.5%. Add to that the income from the alt coins and the fee is negative. Disclaimer: I'm a tad biased...@Doublec,
above your comment in the Bitminter vs. Eligius thread. Any explanation why the orphan rate is much higher than expected. There are 8 orphan out of 188 blocks since the DGM-switch. This equals 4.2% ophans, much more than normal! Now it matters, because you are not paying orphan blocks anymore. Taking your numbers, the effective Bitparking fee is 4,7%.
OK total breakdown is happening again... Only 3.1.1 affected. Log in PM...
I've made a configuration change just now. Let me know if it makes a difference.EDIT: Log PM
OK total breakdown is happening again... Only 3.1.1 affected. Log in PM...
I've made a configuration change just now. Let me know if it makes a difference.
OK total breakdown is happening again... Only 3.1.1 affected. Log in PM...
EDIT: Just figure it out. It was late yesterday. Should I add --protocol-dump too?
Yes, protocol-dump would be useful,thanks.EDIT: and there are practically no disconnects...
EDIT: Just figure it out. It was late yesterday. Should I add --protocol-dump too?
Yes, protocol-dump would be useful,thanks.
Log file send(see PM). Hope it helps. Over the night it wasn't so bed, but there were disconnects...
EDIT: Just figure it out. It was late yesterday. Should I add --protocol-dump too?
EDIT: Just figure it out. It was late yesterday. Should I add --protocol-dump too?
Sorry but it is getting unbearable. Backup pool see me with 300HM+ at the moment... I'm switching to backup my 3.1.1 miner. Please help...
Can you turn on verbose logging of cgminer, including protocol logging, and log to a file? When you get a disconnect like this send me the log and it'll help track it down, thanks.Getwork server is currently offline while I investigate some issues.
Getwork server is operational again. Jump to: