OgiDogi
Newbie
Offline
Activity: 4
Merit: 0
|
|
June 01, 2011, 06:28:06 AM |
|
Is there someone who still can't reach the website ?
Neither client connects nor page loads from home (46.40.126.x) while deepbit.net is loading fine from work (different internet provider). Mozilla says "connecting to deepbit.net" when I try to load the page and "server timed out" afterwards. It was 9 hops several days ago when I traced, now it is 23 hops: 1 1 ms 1 ms 1 ms static-gw.bulsat.com [46.40.126.1] 2 1 ms 1 ms 1 ms static-gw.bulsat.com [46.40.126.1] 3 6 ms 6 ms 6 ms jun-mx960.intl.bulsat.com [46.40.68.1] 4 6 ms 6 ms 6 ms 46.40.73.194 5 6 ms 7 ms 7 ms 195.81.49.102 6 6 ms 6 ms 6 ms 195.81.49.121 7 50 ms 36 ms 37 ms ae2-0.bud-001-score-1-re0.interoute.net [84.233.193.198] 8 36 ms 36 ms 36 ms ae2-0.prg-001-score-2-re0.interoute.net [84.233.138.213] 9 36 ms 37 ms 36 ms ae0-0.prg-001-score-1-re0.interoute.net [84.233.138.205] 10 36 ms 37 ms 36 ms ae2-0.fra-006-score-2-re0.interoute.net [84.233.138.210] 11 36 ms 37 ms 74 ms ae1-0.fra-006-score-3-re0.interoute.net [212.23.42.174] 12 41 ms 41 ms 42 ms xe-1-2-0.mpr1.fra4.de.above.net [80.81.194.26] 13 62 ms 53 ms 46 ms xe-1-1-0.mpr1.cdg12.fr.above.net [64.125.24.6] 14 58 ms 59 ms 59 ms xe-4-0-0.mpr1.lhr3.uk.above.net [64.125.31.249] 15 127 ms 128 ms 127 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41] 16 161 ms 161 ms 185 ms xe-0-2-0.cr2.iah1.us.above.net [64.125.28.50] 17 216 ms 189 ms 189 ms xe-2-0-0.cr2.lax112.us.above.net [64.125.25.18] 18 189 ms 189 ms 188 ms xe-0-1-0.er2.lax112.us.above.net [64.125.30.249] 19 190 ms 190 ms 195 ms 64.124.161.210.allocated.above.net [64.124.161.210] 20 187 ms 187 ms 187 ms edge07-ge.lax1.staminus.net [72.20.0.7] 21 190 ms 190 ms 189 ms sp03.lax1.staminus.net [72.20.0.17] 22 190 ms 192 ms 190 ms aggr-sw2-ge.lax1.staminus.net [72.20.0.44] 23 190 ms 190 ms 190 ms . [72.8.190.23]
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
sniper_sniperson
|
|
June 01, 2011, 06:59:08 AM |
|
Looks like someone rerouted the river through InteRoute points. This happens on Megalan too so I can predict that the problem is not in our country.
Can you check last 2 hops IP addresses before mining.bitcoin.cz? Route to this pool is also changed - another 8 hops through InteRoute.
|
|
|
|
minerX
Newbie
Offline
Activity: 56
Merit: 0
|
|
June 01, 2011, 07:02:59 AM |
|
I just had 5 long polls in a row about 8 minutes apart from each other. Then nothing. I switched to standard Poclbm.exe.
|
|
|
|
bongo
Newbie
Offline
Activity: 9
Merit: 0
|
|
June 01, 2011, 07:06:47 AM |
|
I've been on since it was a 30gh pool, but its time to move on. Hope all is resolved soon.
|
|
|
|
Timba
Newbie
Offline
Activity: 7
Merit: 0
|
|
June 01, 2011, 07:48:16 AM |
|
Problem with access to pool present... trace to server (may be it help?) 1 2 ms <1 ìñ 2 ms hub [192.168.192.254]
2 3 ms 1 ms <1 ìñ modem [192.168.1.1]
3 57 ms 39 ms 39 ms 95-55-16-1.dynamic.avangarddsl.ru [95.55.16.1]
4 54 ms 41 ms 39 ms xe-2-1-1.10g.t1600-2-210.nwtelecom.ru [212.48.198.181]
5 39 ms 38 ms 41 ms ae1.30g.mx960-1-210.nwtelecom.ru [212.48.198.250]
6 38 ms 38 ms 38 ms ae5.RT.POL.SPB.RU.retn.net [87.245.252.101]
7 228 ms 227 ms 229 ms so100.RT.CRG.LAX.US.retn.net [87.245.233.170]
8 * * *
9 227 ms 226 ms 226 ms edge07-ge.lax1.staminus.net [72.20.0.7]
10 227 ms 227 ms 226 ms sp03.lax1.staminus.net [72.20.0.17]
11 226 ms 229 ms 226 ms aggr-sw2-ge.lax1.staminus.net [72.20.0.44]
12 227 ms 226 ms 226 ms deepbit.net [72.8.190.23]
|
|
|
|
dourox11uk
Newbie
Offline
Activity: 9
Merit: 0
|
|
June 01, 2011, 08:08:29 AM |
|
Hello Tycho,
Would be nice to see stats for all days since beginning
Thanks
|
|
|
|
daehbe
Newbie
Offline
Activity: 2
Merit: 0
|
|
June 01, 2011, 08:54:41 AM |
|
hi, just wondering is the long polling working okay now? I got some workers up to 10% stales...
|
|
|
|
gentakin
Member
Offline
Activity: 98
Merit: 10
|
|
June 01, 2011, 08:58:19 AM |
|
hi, just wondering is the long polling working okay now? I got some workers up to 10% stales...
Works for me (phoenix). You might have to restart your miner.
|
1HNjbHnpu7S3UUNMF6J9yWTD597LgtUCxb
|
|
|
luffy
|
|
June 01, 2011, 09:01:58 AM |
|
Go tycho go! please only put the fee back up to 2% XD
not even 4% is enough for all his hard work! it seems like he is a bot or something (no personal life?!)
|
|
|
|
SomeoneWeird
|
|
June 01, 2011, 09:05:13 AM |
|
Go tycho go! please only put the fee back up to 2% XD
not even 4% is enough for all his hard work! it seems like he is a bot or something (no personal life?!) With the income he makes he probably doesn't even need a job.
|
|
|
|
daehbe
Newbie
Offline
Activity: 2
Merit: 0
|
|
June 01, 2011, 09:12:37 AM |
|
and can I put all the miners under one single worker? or are all the miners doing the same work so it's just a waste?
|
|
|
|
lvlrdka22
|
|
June 01, 2011, 09:21:04 AM |
|
Just to put it into perspective: At 1262 GH/s, average time for finding a block is 24.66 minutes, which is about 1780 blocks per month, or 89k BTC per month. If everyone used proportional at 3% (the old rate), he's making 2670 BTC per month. If everyone used PPS at 10% (heard that somewhere, not sure of the exact rate), he's making 8900 BTC per month. That translates to 23k/77k (somewhere between there, since not everyone uses proportional) per month. Subtract some utility fees. Untaxed.
Who needs a job with an income like that?
|
|
|
|
tccd
Newbie
Offline
Activity: 51
Merit: 0
|
|
June 01, 2011, 09:57:58 AM |
|
"The connection to the server was reset while the page was loading." 1 <1 ms <1 ms <1 ms 192.168.0.27 2 1 ms 1 ms 1 ms 192.168.1.1 3 * * * Request timed out. 4 33 ms 32 ms 41 ms 212.39.69.228 5 34 ms 33 ms 33 ms 212.39.69.225 6 33 ms 32 ms 33 ms sfia-b2-link.telia.net [213.248.85.217] 7 53 ms 52 ms 53 ms win-bb2-link.telia.net [80.91.247.108] 8 66 ms 66 ms 66 ms ffm-bb2-link.telia.net [80.91.246.142] 9 67 ms 69 ms 76 ms ffm-b2-link.telia.net [80.91.247.169] 10 78 ms 64 ms 63 ms abovenet-ic-136942-ffm-b2.c.telia.net [213.248.9 .146] 11 108 ms 124 ms 77 ms xe-1-1-0.mpr1.cdg12.fr.above.net [64.125.24.6] 12 89 ms 89 ms 90 ms xe-4-0-0.mpr1.lhr3.uk.above.net [64.125.31.249]
13 159 ms 157 ms 169 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41] 14 193 ms 193 ms 192 ms xe-0-2-0.cr2.iah1.us.above.net [64.125.28.50] 15 232 ms 242 ms 241 ms xe-0-3-0.cr2.lax112.us.above.net [64.125.30.50]
16 218 ms 218 ms 232 ms xe-0-1-0.er2.lax112.us.above.net [64.125.30.249]
17 300 ms 269 ms 369 ms 64.124.161.210.allocated.above.net [64.124.161.2 0] 18 217 ms 253 ms 217 ms edge07-ge.lax1.staminus.net [72.20.0.7] 19 257 ms 227 ms 228 ms sp03.lax1.staminus.net [72.20.0.17] 20 241 ms 229 ms 230 ms aggr-sw2-ge.lax1.staminus.net [72.20.0.44] 21 218 ms 218 ms 219 ms . [72.8.190.23]
|
|
|
|
Timba
Newbie
Offline
Activity: 7
Merit: 0
|
|
June 01, 2011, 10:53:46 AM |
|
Again tests... ping to deepbit.net now successful. But Guimmer and bitcoin-miner - clients don't work. And site deepbit.net unaccessible too.
|
|
|
|
borgfish
Member
Offline
Activity: 75
Merit: 10
|
|
June 01, 2011, 12:47:08 PM |
|
verification failed, check your hardware
i used my core2quad 3ghz. 3,8mh/s and seem to be having no results so far. is this a common error in cpu hashing ? how many mh (absolute, not per second) would i probably need to have some noticeable result like 0.00000001 BTC in my deepbit account ?
|
|
|
|
PolymorphicAssasin
Newbie
Offline
Activity: 46
Merit: 0
|
|
June 01, 2011, 01:15:11 PM |
|
Hey all - been lurking here for 4-5 days now, first post. Good work by Tycho - nice pool. I see people 'complaining' about fees, but it's free enterprise. Kudos to him and his team for making a nice living providing a service that people want. Issue: Miners at home plugged along fairly well since DDOS attach, but last night I wasn't able to reach the website at all to check stats. I could ping both pit.deepbit.net and deepbit.net, so no connectivity issue that I could figure. Didn't have much time to troubleshoot so I just switched them over to another pool. Here at the office, am able to hit the website no problem, but lots of issues with the communication on the Miner: Both Home and Office are on Comcast internet, about 8 miles apart. 2011-05-31 18:27:05: Listener for "DeepBit": 31/05/2011 18:27:05, warning: job finished, miner is idle 2011-05-31 18:27:07: Listener for "DeepBit": 31/05/2011 18:27:07, Problems communicating with bitcoin RPC 2011-05-31 18:27:13: Listener for "DeepBit": 31/05/2011 18:27:13, Problems communicating with bitcoin RPC 2011-05-31 18:27:19: Listener for "DeepBit": 31/05/2011 18:27:19, Problems communicating with bitcoin RPC 2011-05-31 18:27:25: Listener for "DeepBit": 31/05/2011 18:27:25, Problems communicating with bitcoin RPC 2011-05-31 18:27:56: Listener for "DeepBit": 31/05/2011 18:27:56, long poll: new block 00001b82662aa78b 2011-05-31 18:28:58: Listener for "DeepBit": 31/05/2011 18:28:58, long poll: new block 0000076213288746 2011-05-31 18:31:18: Listener for "DeepBit": 31/05/2011 18:31:18, long poll: new block 00001edfcce6d535 2011-05-31 18:39:22: Listener for "DeepBit": 31/05/2011 18:39:22, long poll: new block 000007dbd31851c9 2011-05-31 18:51:47: Listener for "DeepBit": 31/05/2011 18:51:47, long poll: new block 00001795fb84a755 2011-05-31 19:23:14: Listener for "DeepBit": 31/05/2011 19:23:14, long poll: new block 0000137965b1270e 2011-05-31 19:26:26: Listener for "DeepBit": 31/05/2011 19:26:26, long poll: new block 000007573578cf86 2011-05-31 19:29:20: Listener for "DeepBit": 31/05/2011 19:29:20, long poll: new block 00001e6c48e5105f 2011-05-31 19:34:01: Listener for "DeepBit": 31/05/2011 19:34:01, long poll: new block 000004121802f73b 2011-05-31 19:43:40: Listener for "DeepBit": 31/05/2011 19:43:40, long poll: new block 00001bf4a71f84d9 2011-05-31 19:53:07: Listener for "DeepBit": 31/05/2011 19:53:07, long poll: new block 00001d5d770f2756 2011-05-32011-05-31 19:56:42: Listener for "DeepBit": 31/05/2011 19:56:42, long poll: new block 000013622c87250c 2011-05-31 20:03:29: Listener for "DeepBit": 31/05/2011 20:03:29, long poll: new block 00001f2a52ce9e30 2011-05-31 20:11:23: Listener for "DeepBit": 31/05/2011 20:11:23, long poll: new block 0000099724b15ebd 2011-05-31 20:14:41: Listener for "DeepBit": 31/05/2011 20:14:41, long poll: new block 00000e4e34b44d6e 2011-05-31 20:26:34: Listener for "DeepBit": 31/05/2011 20:26:34, long poll: new block 000022e426c24cd6 2011-05-31 20:32:02: Listener for "DeepBit": 31/05/2011 20:32:02, long poll: new block 000025e74442e871 2011-05-31 20:33:21: Listener for "DeepBit": 31/05/2011 20:33:21, long poll: new block 00000dc000ce518d 2011-05-31 20:42:04: Listener for "DeepBit": 31/05/2011 20:42:04, long poll: new block 00000e312b15bd1b 2011-05-31 21:04:42: Listener for "DeepBit": 31/05/2011 21:04:42, long poll: new block 000014c8ede8c55c 2011-05-31 21:12:29: Listener for "DeepBit": 31/05/2011 21:12:29, long poll: new block 00001da0a3a4afab 2011-05-31 21:17:18: Listener for "DeepBit": 31/05/2011 21:17:18, Problems communicating with bitcoin RPC 2011-05-31 21:18:45: Listener for "DeepBit": 31/05/2011 21:18:45, long poll: Long polling is restarting, this doesn't effect mining 2011-05-31 21:18:49: Listener for "DeepBit": 31/05/2011 21:18:49, long poll exception: 2011-05-31 21:19:17: Listener for "DeepBit": 31/05/2011 21:19:17, Problems communicating with bitcoin RPC 2011-05-31 21:19:33: Listener for "DeepBit": 31/05/2011 21:19:33, long poll: Long polling is restarting, this doesn't effect mining 2011-05-31 21:19:37: Listener for "DeepBit": 31/05/2011 21:19:37, long poll exception: 2011-05-31 21:25:29: Listener for "DeepBit": 31/05/2011 21:25:29, Problems communicating with bitcoin RPC 2011-05-31 21:26:13: Listener for "DeepBit": 31/05/2011 21:26:13, Problems communicating with bitcoin RPC 2011-05-31 21:28:52: Listener for "DeepBit": 31/05/2011 21:28:52, long poll: new block 00001d4e4d4c0a09 2011-05-31 21:28:58: Listener for "DeepBit": 31/05/2011 21:28:58, long poll exception: 2011-05-31 21:29:55: Listener for "DeepBit": 31/05/2011 21:29:55, Problems communicating with bitcoin RPC 2011-05-31 21:30:22: Listener for "DeepBit": 31/05/2011 21:30:22, long poll: new block 00002489206f250a 2011-05-31 21:30:26: Listener for "DeepBit": 31/05/2011 21:30:26, long poll exception: 2011-05-31 21:37:26: Listener for "DeepBit": 31/05/2011 21:37:26, Problems communicating with bitcoin RPC 2011-05-31 21:38:30: Listener for "DeepBit": 31/05/2011 21:38:30, Problems communicating with bitcoin RPC 2011-05-31 21:39:36: Listener for "DeepBit": 31/05/2011 21:39:36, long poll: new block 0000194e8e813aaf 2011-05-31 21:39:45: Listener for "DeepBit": 31/05/2011 21:39:45, long poll exception: 2011-05-31 21:42:07: Listener for "DeepBit": 31/05/2011 21:42:07, Problems communicating with bitcoin RPC 2011-05-31 21:44:30: Listener for "DeepBit": 31/05/2011 21:44:30, Problems communicating with bitcoin RPC 2011-05-31 21:44:48: Listener for "DeepBit": 31/05/2011 21:44:48, long poll: new block 000015c4fa853e39 2011-05-31 21:44:55: Listener for "DeepBit": 31/05/2011 21:44:55, long poll exception: 2011-05-31 21:45:21: Listener for "DeepBit": 31/05/2011 21:45:21, Problems communicating with bitcoin RPC 2011-05-31 21:48:06: Listener for "DeepBit": 31/05/2011 21:48:06, long poll: new block 000025035f1718f1 2011-05-31 21:48:13: Listener for "DeepBit": 31/05/2011 21:48:13, long poll exception: 2011-05-31 21:50:37: Listener for "DeepBit": 31/05/2011 21:50:37, long poll: new block 00000256ae959b7a 2011-05-31 21:53:29: Listener for "DeepBit": 31/05/2011 21:53:29, Problems communicating with bitcoin RPC 2011-05-31 22:11:57: Listener for "DeepBit": 31/05/2011 22:11:57, long poll: new block 00001e7fe0cb859d 2011-05-31 22:12:03: Listener for "DeepBit": 31/05/2011 22:12:03, long poll exception: 2011-05-31 22:18:43: Listener for "DeepBit": 31/05/2011 22:18:43, long poll: new block 0000236f285b1278 2011-05-31 22:21:20: Listener for "DeepBit": 31/05/2011 22:21:20, long poll: new block 000006c17f522b2d 2011-05-31 22:23:52: Listener for "DeepBit": 31/05/2011 22:23:52, long poll: new block 000018a0725f73de 2011-05-31 22:26:40: Listener for "DeepBit": 31/05/2011 22:26:40, long poll: new block 0000072dbbd8d02c 2011-05-31 22:29:28: Listener for "DeepBit": 31/05/2011 22:29:28, long poll: new block 00001ed89acd0835 2011-05-31 22:48:26: Listener for "DeepBit": 31/05/2011 22:48:26, long poll: new block 00001846d656f598 2011-05-31 23:01:31: Listener for "DeepBit": 31/05/2011 23:01:31, warning: job finished, miner is idle 2011-05-31 23:01:32: Listener for "DeepBit": 31/05/2011 23:01:32, Problems communicating with bitcoin RPC 2011-05-31 23:01:37: Listener for "DeepBit": 31/05/2011 23:01:37, Problems communicating with bitcoin RPC 2011-05-31 23:01:43: Listener for "DeepBit": 31/05/2011 23:01:43, Problems communicating with bitcoin RPC 2011-05-31 23:03:30: Listener for "DeepBit": 31/05/2011 23:03:30, warning: job finished, miner is idle 2011-05-31 23:03:31: Listener for "DeepBit": 31/05/2011 23:03:31, Problems communicating with bitcoin RPC 2011-05-31 23:03:37: Listener for "DeepBit": 31/05/2011 23:03:37, Problems communicating with bitcoin RPC 2011-05-31 23:03:42: Listener for "DeepBit": 31/05/2011 23:03:42, long poll: new block 000001994ebbd2f4 2011-05-31 23:03:43: Listener for "DeepBit": 31/05/2011 23:03:43, Problems communicating with bitcoin RPC 2011-05-31 23:05:07: Listener for "DeepBit": 31/05/2011 23:05:07, long poll: new block 000008c10fd9ffd4 2011-05-31 23:05:13: Listener for "DeepBit": 31/05/2011 23:05:13, long poll exception: 2011-05-31 23:05:25: Listener for "DeepBit": 31/05/2011 23:05:25, long poll: Long polling is restarting, this doesn't effect mining 2011-05-31 23:05:27: Listener for "DeepBit": 31/05/2011 23:05:27, Problems communicating with bitcoin RPC 2011-05-31 23:05:33: Listener for "DeepBit": 31/05/2011 23:05:33, Problems communicating with bitcoin RPC 2011-05-31 23:05:39: Listener for "DeepBit": 31/05/2011 23:05:39, Problems communicating with bitcoin RPC 2011-05-31 23:05:45: Listener for "DeepBit": 31/05/2011 23:05:45, Problems communicating with bitcoin RPC 2011-05-31 23:05:51: Listener for "DeepBit": 31/05/2011 23:05:51, Problems communicating with bitcoin RPC 2011-05-31 23:05:58: Listener for "DeepBit": 31/05/2011 23:05:58, Problems communicating with bitcoin RPC 2011-05-31 23:06:04: Listener for "DeepBit": 31/05/2011 23:06:04, Problems communicating with bitcoin RPC 2011-05-31 23:06:10: Listener for "DeepBit": 31/05/2011 23:06:10, Problems communicating with bitcoin RPC 2011-05-31 23:06:16: Listener for "DeepBit": 31/05/2011 23:06:16, Problems communicating with bitcoin RPC 2011-05-31 23:06:17: Listener for "DeepBit": 31/05/2011 23:06:17, Problems communicating with bitcoin RPC 2011-05-31 23:06:21: Listener for "DeepBit": 31/05/2011 23:06:21, Problems communicating with bitcoin RPC 2011-05-31 23:06:23: Listener for "DeepBit": 31/05/2011 23:06:23, Problems communicating with bitcoin RPC 2011-05-31 23:06:29: Listener for "DeepBit": 31/05/2011 23:06:29, Problems communicating with bitcoin RPC 2011-05-31 23:06:30: Listener for "DeepBit": 31/05/2011 23:06:30, Problems communicating with bitcoin RPC 2011-05-31 23:06:36: Listener for "DeepBit": 31/05/2011 23:06:36, Problems communicating with bitcoin RPC 2011-05-31 23:06:38: Listener for "DeepBit": 31/05/2011 23:06:38, Problems communicating with bitcoin RPC 2011-05-31 23:06:41: Listener for "DeepBit": 31/05/2011 23:06:41, long poll exception: 2011-06-01 06:58:20: Listener for "DeepBit": 01/06/2011 06:58:20, warning: job finished, miner is idle 2011-06-01 06:58:21: Listener for "DeepBit": 01/06/2011 06:58:21, Problems communicating with bitcoin RPC
I'm UTC - 5hrs, so if that helps with the time offset. If it helps any, here's the tracert from my office to your server: Tracing route to pit.deepbit.net [72.8.190.23] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.10.12.1 2 9 ms 11 ms 9 ms 73.37.xxx.x 3 9 ms 8 ms 9 ms ge-1-21-ur01.grandrapids.mi.michigan.comcast.net [68.85.48.137] 4 9 ms 9 ms 9 ms te-9-2-ur02.grandrapids.mi.michigan.comcast.net [68.87.191.222] 5 17 ms 19 ms 19 ms te-0-7-0-1-ar01.pontiac.mi.michigan.comcast.net [68.85.222.226] 6 30 ms 27 ms 28 ms pos-3-3-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.109] 7 29 ms 28 ms 28 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.158] 8 28 ms 28 ms 28 ms 66.208.229.254 9 28 ms 28 ms 31 ms xe-2-1-0.cr2.ord2.us.above.net [64.125.26.253] 10 96 ms 92 ms 100 ms xe-0-2-0.cr2.sjc2.us.above.net [64.125.26.141] 11 104 ms 102 ms 100 ms xe-2-1-0.cr2.lax112.us.above.net [64.125.26.29] 12 200 ms 100 ms 103 ms xe-1-1-0.er2.lax112.us.above.net [64.125.30.253] 13 101 ms 102 ms 100 ms 64.124.161.210.allocated.above.net [64.124.161.210] 14 100 ms 100 ms 100 ms edge04-ge.lax1.staminus.net [72.20.0.4] 15 102 ms 103 ms 103 ms sp03.lax1.staminus.net [72.20.0.17] 16 102 ms 104 ms 102 ms aggr-sw2-ge.lax1.staminus.net [72.20.0.44] 17 106 ms 100 ms 100 ms . [72.8.190.23]
In any case, I prefer this pool over the others, so this is just me trying to help isolate and solve the issues, no complaint here. I'm only generating about 4-500 Mhash/s anyway.
|
|
|
|
melco
Member
Offline
Activity: 62
Merit: 10
|
|
June 01, 2011, 02:12:20 PM |
|
Hi Is it possible to add stats column on how much BTC worker earned in front of each worker (after "Shares" column)?
|
|
|
|
zimpixa
Member
Offline
Activity: 98
Merit: 10
|
|
June 01, 2011, 03:02:57 PM |
|
To every1 having problem reaching deepbit server.
Did you guys tried restarting your router? It helps in my way and it looks like its very similar situation.
|
|
|
|
[Tycho]
|
|
June 01, 2011, 04:33:45 PM |
|
Is it possible to add stats column on how much BTC worker earned in front of each worker (after "Shares" column)? Currently workers are just a technical entities, only the whole account is credited with BTC. I'll think about it.
|
Welcome to my bitcoin mining pool: https://deepbit.net - Both payment schemes (including PPS), instant payout, no invalid blocks ! ICBIT Trading platform : USD/BTC futures trading, Bitcoin difficulty futures ( NEW!). Third year in bitcoin business.
|
|
|
MiningBuddy
|
|
June 01, 2011, 04:34:52 PM Last edit: August 11, 2011, 09:11:07 PM by MiningBuddy |
|
Whats the latest address one should use to connect miners? pit.deepbit.net or deepbit.net There seems to be conflicting address's on the site.
thanks
|
|
|
|
|