Topic: [ANN] CoinLab Protected Pool - page 38. (Read 97861 times)
I don't know what problems you guys are having, but I just check the rig I have pointed here before I did it's daily restart. I had about 50k accepted, and 2 rejects.
Submissions: 12956 total, 475 rejected, 96.33% efficiency
Rejects are also quite high now
Rejects are also quite high now
I dont see the rejects as much.
here is after about 16 hours of running 2 identical rigs. one against ozcoin pps and one against coinlab. both rigs have a plethora of backup pools and i will get those stats when i shut down cgminer.
as you can see the rig pointed at coinlab is not running as hard (mostly 98%, not 99%), but overall it has had more accepted shares so far.
enjoy
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner9
miner9
(5s):2903.73 (avg): 2898.28 Mh/s | H: 125 Q:25399 A:42883 R:32 HW:0 E:?% U:40.11/m
TQ:? ST:62 SS:? DW:3909 NB:204 LW:147390 GF:9 RF:5
Connected to http://pool.coinlab.com:8332 with LP as user ?
Value:
GPU 0: 70.5C 3178RPM 49% 120 | 362.8/362.6Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5347 R:6 HW:0 U:5.00/m I: 7
GPU 1: 71.5C 3178RPM 49% 121 | 363.3/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5325 R:6 HW:0 U:4.98/m I: 7
GPU 2: 71.5C 3597RPM 59% 131 | 362.3/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5368 R:5 HW:0 U:5.02/m I: 7
GPU 3: 68.5C 3597RPM 59% 128 | 363.4/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5491 R:3 HW:0 U:5.14/m I: 7
GPU 4: 72.0C 3191RPM 49% 121 | 362.9/362.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5218 R:1 HW:0 U:4.88/m I: 7
GPU 5: 70.5C 3189RPM 49% 120 | 363.5/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5337 R:4 HW:0 U:4.99/m I: 7
GPU 6: 68.5C 3741RPM 61% 130 | 363.1/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5439 R:5 HW:0 U:5.09/m I: 7
GPU 7: 71.0C 3741RPM 61% 132 | 362.5/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5358 R:2 HW:0 U:5.01/m I: 7
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner10
miner10
(5s):2905.14 (avg): 2906.98 Mh/s | H: 127.19 Q:28187 A:42651 R:203 HW:0 E:?% U:39.89/m
TQ:? ST:18 SS:? DW:4662 NB:206 LW:113959 GF:7 RF:3
Connected to http://us.ozco.in:8332 with LP as user ?
Value:
GPU 0: 71.5C 3584RPM 60% 132 | 364.0/363.6Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5286 R:26 HW:0 U:4.94/m I: 7
GPU 1: 68.0C 3584RPM 60% 128 | 362.6/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5385 R:22 HW:0 U:5.04/m I: 7
GPU 2: 70.5C 3581RPM 59% 130 | 363.5/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5331 R:17 HW:0 U:4.99/m I: 7
GPU 3: 70.0C 3584RPM 59% 129 | 363.0/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5283 R:23 HW:0 U:4.94/m I: 7
GPU 4: 69.5C 3337RPM 55% 125 | 363.3/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5300 R:22 HW:0 U:4.96/m I: 7
GPU 5: 69.5C 3337RPM 55% 125 | 362.3/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5378 R:35 HW:0 U:5.03/m I: 7
GPU 6: 71.0C 3233RPM 56% 127 | 362.9/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5319 R:28 HW:0 U:4.98/m I: 7
GPU 7: 67.5C 3233RPM 56% 124 | 363.5/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5369 R:30 HW:0 U:5.02/m I: 7
Awesome! Sharing this with the team.
Submissions: 12956 total, 475 rejected, 96.33% efficiency
Rejects are also quite high now
Rejects are also quite high now
I dont see the rejects as much.
here is after about 16 hours of running 2 identical rigs. one against ozcoin pps and one against coinlab. both rigs have a plethora of backup pools and i will get those stats when i shut down cgminer.
as you can see the rig pointed at coinlab is not running as hard (mostly 98%, not 99%), but overall it has had more accepted shares so far.
enjoy
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner9
miner9
(5s):2903.73 (avg): 2898.28 Mh/s | H: 125 Q:25399 A:42883 R:32 HW:0 E:?% U:40.11/m
TQ:? ST:62 SS:? DW:3909 NB:204 LW:147390 GF:9 RF:5
Connected to http://pool.coinlab.com:8332 with LP as user ?
Value:
GPU 0: 70.5C 3178RPM 49% 120 | 362.8/362.6Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5347 R:6 HW:0 U:5.00/m I: 7
GPU 1: 71.5C 3178RPM 49% 121 | 363.3/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5325 R:6 HW:0 U:4.98/m I: 7
GPU 2: 71.5C 3597RPM 59% 131 | 362.3/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5368 R:5 HW:0 U:5.02/m I: 7
GPU 3: 68.5C 3597RPM 59% 128 | 363.4/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5491 R:3 HW:0 U:5.14/m I: 7
GPU 4: 72.0C 3191RPM 49% 121 | 362.9/362.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5218 R:1 HW:0 U:4.88/m I: 7
GPU 5: 70.5C 3189RPM 49% 120 | 363.5/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5337 R:4 HW:0 U:4.99/m I: 7
GPU 6: 68.5C 3741RPM 61% 130 | 363.1/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5439 R:5 HW:0 U:5.09/m I: 7
GPU 7: 71.0C 3741RPM 61% 132 | 362.5/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5358 R:2 HW:0 U:5.01/m I: 7
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner10
miner10
(5s):2905.14 (avg): 2906.98 Mh/s | H: 127.19 Q:28187 A:42651 R:203 HW:0 E:?% U:39.89/m
TQ:? ST:18 SS:? DW:4662 NB:206 LW:113959 GF:7 RF:3
Connected to http://us.ozco.in:8332 with LP as user ?
Value:
GPU 0: 71.5C 3584RPM 60% 132 | 364.0/363.6Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5286 R:26 HW:0 U:4.94/m I: 7
GPU 1: 68.0C 3584RPM 60% 128 | 362.6/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5385 R:22 HW:0 U:5.04/m I: 7
GPU 2: 70.5C 3581RPM 59% 130 | 363.5/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5331 R:17 HW:0 U:4.99/m I: 7
GPU 3: 70.0C 3584RPM 59% 129 | 363.0/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5283 R:23 HW:0 U:4.94/m I: 7
GPU 4: 69.5C 3337RPM 55% 125 | 363.3/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5300 R:22 HW:0 U:4.96/m I: 7
GPU 5: 69.5C 3337RPM 55% 125 | 362.3/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5378 R:35 HW:0 U:5.03/m I: 7
GPU 6: 71.0C 3233RPM 56% 127 | 362.9/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5319 R:28 HW:0 U:4.98/m I: 7
GPU 7: 67.5C 3233RPM 56% 124 | 363.5/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5369 R:30 HW:0 U:5.02/m I: 7
Nice
Submissions: 12956 total, 475 rejected, 96.33% efficiency
Rejects are also quite high now
Rejects are also quite high now
I dont see the rejects as much.
here is after about 16 hours of running 2 identical rigs. one against ozcoin pps and one against coinlab. both rigs have a plethora of backup pools and i will get those stats when i shut down cgminer.
as you can see the rig pointed at coinlab is not running as hard (mostly 98%, not 99%), but overall it has had more accepted shares so far.
enjoy
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner9
miner9
(5s):2903.73 (avg): 2898.28 Mh/s | H: 125 Q:25399 A:42883 R:32 HW:0 E:?% U:40.11/m
TQ:? ST:62 SS:? DW:3909 NB:204 LW:147390 GF:9 RF:5
Connected to http://pool.coinlab.com:8332 with LP as user ?
Value:
GPU 0: 70.5C 3178RPM 49% 120 | 362.8/362.6Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5347 R:6 HW:0 U:5.00/m I: 7
GPU 1: 71.5C 3178RPM 49% 121 | 363.3/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5325 R:6 HW:0 U:4.98/m I: 7
GPU 2: 71.5C 3597RPM 59% 131 | 362.3/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5368 R:5 HW:0 U:5.02/m I: 7
GPU 3: 68.5C 3597RPM 59% 128 | 363.4/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5491 R:3 HW:0 U:5.14/m I: 7
GPU 4: 72.0C 3191RPM 49% 121 | 362.9/362.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5218 R:1 HW:0 U:4.88/m I: 7
GPU 5: 70.5C 3189RPM 49% 120 | 363.5/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5337 R:4 HW:0 U:4.99/m I: 7
GPU 6: 68.5C 3741RPM 61% 130 | 363.1/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5439 R:5 HW:0 U:5.09/m I: 7
GPU 7: 71.0C 3741RPM 61% 132 | 362.5/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:5358 R:2 HW:0 U:5.01/m I: 7
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner10
miner10
(5s):2905.14 (avg): 2906.98 Mh/s | H: 127.19 Q:28187 A:42651 R:203 HW:0 E:?% U:39.89/m
TQ:? ST:18 SS:? DW:4662 NB:206 LW:113959 GF:7 RF:3
Connected to http://us.ozco.in:8332 with LP as user ?
Value:
GPU 0: 71.5C 3584RPM 60% 132 | 364.0/363.6Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5286 R:26 HW:0 U:4.94/m I: 7
GPU 1: 68.0C 3584RPM 60% 128 | 362.6/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5385 R:22 HW:0 U:5.04/m I: 7
GPU 2: 70.5C 3581RPM 59% 130 | 363.5/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5331 R:17 HW:0 U:4.99/m I: 7
GPU 3: 70.0C 3584RPM 59% 129 | 363.0/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5283 R:23 HW:0 U:4.94/m I: 7
GPU 4: 69.5C 3337RPM 55% 125 | 363.3/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5300 R:22 HW:0 U:4.96/m I: 7
GPU 5: 69.5C 3337RPM 55% 125 | 362.3/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5378 R:35 HW:0 U:5.03/m I: 7
GPU 6: 71.0C 3233RPM 56% 127 | 362.9/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5319 R:28 HW:0 U:4.98/m I: 7
GPU 7: 67.5C 3233RPM 56% 124 | 363.5/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:5369 R:30 HW:0 U:5.02/m I: 7
Submissions: 12956 total, 475 rejected, 96.33% efficiency
Rejects are also quite high now
Rejects are also quite high now
I've been getting this quite often:
Using guiminer with the 20 Sep version of poclbm.
Code:
2012-10-11 11:21:04: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:21:04, Still unable to reconnect to primary server (attempt 1), failing over
2012-10-11 11:21:04: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:21:04, checking for stratum...
2012-10-11 11:21:09: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:21:09, no response to getwork, using as stratum
2012-10-11 11:21:09: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:21:09, No JSON object could be decoded
2012-10-11 11:21:19: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:21:19, Failed to subscribe
2012-10-11 11:21:21: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:21:21, IO errors - 1, tolerance 2
2012-10-11 11:22:22: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:22:22, Attempting to fail back to primary server
2012-10-11 11:22:22: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:22:22, checking for stratum...
2012-10-11 11:22:27: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:22:27, no response to getwork, using as stratum
2012-10-11 11:22:27: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:22:27, No JSON object could be decoded
2012-10-11 11:22:37: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:22:37, Failed to subscribe
2012-10-11 11:22:39: Listener for "Default": pool.coinlab.com:8332 11/10/2012 11:22:39, Still unable to reconnect to primary server (attempt 2), failing over
Using guiminer with the 20 Sep version of poclbm.
Server connection has been awful here.
How much can CoinLab handle ?
How much can CoinLab handle ?
Code:
[11/10/2012 16:25:26] Result: 9fbb4d91 accepted
[11/10/2012 16:25:34] Result: 34dbb3fd accepted
[11/10/2012 16:26:03] Disconnected from server
[11/10/2012 16:26:08] Warning: work queue empty, miner is idle
[11/10/2012 16:26:13] Result: 6ea29492 rejected
[11/10/2012 16:26:18] Result: 568d09d6 rejected
[11/10/2012 16:26:19] Connected to server
[11/10/2012 16:26:24] Disconnected from server
[11/10/2012 16:26:27] Result: eb9dedef accepted
[11/10/2012 16:26:28] Warning: work queue empty, miner is idle
[11/10/2012 16:26:28] Connected to server
[11/10/2012 16:26:33] Disconnected from server
[11/10/2012 16:26:37] Warning: work queue empty, miner is idle
[11/10/2012 16:26:40] Result: 43ea5ac5 rejected
[11/10/2012 16:26:40] Connected to server
[11/10/2012 16:26:50] Result: 629b1247 rejected
[11/10/2012 16:27:07] Result: 66d33a40 rejected
[11/10/2012 16:27:35] Result: bfbfb2f0 rejected
[11/10/2012 16:27:56] Result: 4be7fe1c rejected
[11/10/2012 16:28:00] Result: 03aec283 accepted
[11/10/2012 16:28:01] Result: 1eea4df2 accepted
[11/10/2012 16:28:05] Result: 916b9843 accepted
I am running a test right now, but from my initial observations i do get more leaked shares to other pools using cgminer.
Doesn't your miner get work from other pools if it is not busy enough?
Hello Coinlab, your servers are/were doing something funny again. They started around 1830 UTC yesterday. I noticed at around 2330 UTC and switched over to BTCguild. If you guys can confirm you were playing around and you've stopped now I'll switch back.
ETA desired feature: send an email out whenever you mess around with the servers, explaining when you started and when you're likely to finish!
ETA desired feature: send an email out whenever you mess around with the servers, explaining when you started and when you're likely to finish!
Looking into it now.
IS there any update in ETA as to when the client software will be avail / when these HPC projects are coming around? I remember a couple months ago, it was quoted "a couple months" ... well its a couple months later and no word regarding either of those =(
We're planning to release the Beta of our client software on 11/1, with the first HPC test work units coming on soon after.
I think you mean 1st November?
I know it is a minor thing, but in this international community keeping confusion to a minimum is a bonus
Good work on the article
best
Graet
Yep. We're American, and I forget that we sometimes do things backwards from the rest of the world.
The client is slated to come out on November 1st, 2012
Server connection has been awful here.
How much can CoinLab handle ?
How much can CoinLab handle ?
Code:
[11/10/2012 16:25:26] Result: 9fbb4d91 accepted
[11/10/2012 16:25:34] Result: 34dbb3fd accepted
[11/10/2012 16:26:03] Disconnected from server
[11/10/2012 16:26:08] Warning: work queue empty, miner is idle
[11/10/2012 16:26:13] Result: 6ea29492 rejected
[11/10/2012 16:26:18] Result: 568d09d6 rejected
[11/10/2012 16:26:19] Connected to server
[11/10/2012 16:26:24] Disconnected from server
[11/10/2012 16:26:27] Result: eb9dedef accepted
[11/10/2012 16:26:28] Warning: work queue empty, miner is idle
[11/10/2012 16:26:28] Connected to server
[11/10/2012 16:26:33] Disconnected from server
[11/10/2012 16:26:37] Warning: work queue empty, miner is idle
[11/10/2012 16:26:40] Result: 43ea5ac5 rejected
[11/10/2012 16:26:40] Connected to server
[11/10/2012 16:26:50] Result: 629b1247 rejected
[11/10/2012 16:27:07] Result: 66d33a40 rejected
[11/10/2012 16:27:35] Result: bfbfb2f0 rejected
[11/10/2012 16:27:56] Result: 4be7fe1c rejected
[11/10/2012 16:28:00] Result: 03aec283 accepted
[11/10/2012 16:28:01] Result: 1eea4df2 accepted
[11/10/2012 16:28:05] Result: 916b9843 accepted
Hello Coinlab, your servers are/were doing something funny again. They started around 1830 UTC yesterday. I noticed at around 2330 UTC and switched over to BTCguild. If you guys can confirm you were playing around and you've stopped now I'll switch back.
ETA desired feature: send an email out whenever you mess around with the servers, explaining when you started and when you're likely to finish!
ETA desired feature: send an email out whenever you mess around with the servers, explaining when you started and when you're likely to finish!
IS there any update in ETA as to when the client software will be avail / when these HPC projects are coming around? I remember a couple months ago, it was quoted "a couple months" ... well its a couple months later and no word regarding either of those =(
We're planning to release the Beta of our client software on 11/1, with the first HPC test work units coming on soon after.
I think you mean 1st November?
I know it is a minor thing, but in this international community keeping confusion to a minimum is a bonus
Good work on the article
best
Graet
My intention was not to take the thread offtopic or be silly
maybe I should have just pmmed....
IS there any update in ETA as to when the client software will be avail / when these HPC projects are coming around? I remember a couple months ago, it was quoted "a couple months" ... well its a couple months later and no word regarding either of those =(
We're planning to release the Beta of our client software on 11/1, with the first HPC test work units coming on soon after.
I think you mean 1st November?
I know it is a minor thing, but in this international community keeping confusion to a minimum is a bonus
Good work on the article
best
Graet
jftr if he'd written 11/11 I would have thought Armistice Day.
IS there any update in ETA as to when the client software will be avail / when these HPC projects are coming around? I remember a couple months ago, it was quoted "a couple months" ... well its a couple months later and no word regarding either of those =(
We're planning to release the Beta of our client software on 11/1, with the first HPC test work units coming on soon after.
I think you mean 1st November?
I know it is a minor thing, but in this international community keeping confusion to a minimum is a bonus
Good work on the article
best
Graet
IS there any update in ETA as to when the client software will be avail / when these HPC projects are coming around? I remember a couple months ago, it was quoted "a couple months" ... well its a couple months later and no word regarding either of those =(
We're planning to release the Beta of our client software on 11/1, with the first HPC test work units coming on soon after.
I think you mean 1st November?
I know it is a minor thing, but in this international community keeping confusion to a minimum is a bonus
Good work on the article
best
Graet
HPC Wire just ran an article about us!
http://www.hpcwire.com/hpcwire/2012-10-09/digital_gold_rush_powered_by_gpus.html?featured=top
http://www.hpcwire.com/hpcwire/2012-10-09/digital_gold_rush_powered_by_gpus.html?featured=top
Well, they sort of got it right. I do hope that this article will get some interest for you guys. We built it, now let's hope they come.
HPC Wire just ran an article about us!
http://www.hpcwire.com/hpcwire/2012-10-09/digital_gold_rush_powered_by_gpus.html?featured=top
http://www.hpcwire.com/hpcwire/2012-10-09/digital_gold_rush_powered_by_gpus.html?featured=top
IS there any update in ETA as to when the client software will be avail / when these HPC projects are coming around? I remember a couple months ago, it was quoted "a couple months" ... well its a couple months later and no word regarding either of those =(
We're planning to release the Beta of our client software on 11/1, with the first HPC test work units coming on soon after.
Let the miners decide. they will have to experiment with some cards are good for x work and some cards are good for y work
x work pays .5btc per work unit (7970 taking an hour)
y work pays .0003 btc per work unit. (nvidia good for this type)
z work pays .00001690 btc per unit (hell, a cpu might work)
I am just trying to think of the KISS method.
offer the work at price x (accessed thru json of course) and miners will mine it. if they are not profitable, they wont mine it....
giving an estimate of btcperhour is nice, but until you actually do the work, you wont know.
x work pays .5btc per work unit (7970 taking an hour)
y work pays .0003 btc per work unit. (nvidia good for this type)
z work pays .00001690 btc per unit (hell, a cpu might work
)I am just trying to think of the KISS method.
offer the work at price x (accessed thru json of course) and miners will mine it. if they are not profitable, they wont mine it....
giving an estimate of btcperhour is nice, but until you actually do the work, you wont know.
I second this. Take the BOINC approach and create a standard workunit and let the crunchers figure out the comparisons. Believe me, they'll have it worked out PDQ.
OK, I'll share your thoughts with the team.
Coinlab is working diligently on the client and selling compute jobs based on my conversations with Chris.
This is going to be a very nice income for all of us with GPU clusters.
My experience so far in dealing with the folks at Coinlab has been top notch. This is not another fly-by-night BTC operation.
They are a legitimate corporation with funding and expert personnel.
This is going to be a very nice income for all of us with GPU clusters.
My experience so far in dealing with the folks at Coinlab has been top notch. This is not another fly-by-night BTC operation.
They are a legitimate corporation with funding and expert personnel.
I can only hope, cuz many others promised the same and we all got screwed in the end =/
Would be nice if someone actually follows through in the btc community =)
Jump to: