[DOWN] Bitlc.net - P2SH, No invalid blocks, Custom payouts, EU, 0% fee, LP

[Oldminer]

tested pool with 1 Ghash/s the last 12h. I had a very high rate of rejected shares (2%-5%).

I will come back when thats solved.

Besides that I like the pool!

^^

[1714161262]

1714161262

[1714161262]

1714161262

[1714161262]

1714161262

[lizthegrey]

tested pool with 1 Ghash/s the last 12h. I had a very high rate of rejected shares (2%-5%).

I will come back when thats solved.

Besides that I like the pool!

^^

My stale share % with deepbit was 0.5%, but I'm willing to accept that bitcoins.lc is going to have a larger stale share % due to being in Europe rather than US where I'm located.

[btcLeger]

Rejected shares are mostly a problem on the client side, not the pool side. And 2% is excellent, by the way.

One 400Mhash miner got 10% stale the last 2h. Any idea or suggestion why its 0.2% at deepbit with the same miners if its client side?  Never had so high rates so far and I've been through 5 pools now.

[btcLeger]

Ok, in that case it's probably latency. So it's client side because you live in the wrong part of the world Fortunately 2% are quickly outweighed by the fees at Deepbit. But I agree, for me DeepBit's stale shares are exceptionally low as well (back when I mined there, but I don't expect it got worse.)

hmmmm... pings to deepbit.net = around 40ms, pings to mining.bitcoin.cz = around 42ms

doesnt seem like a latency problem to me....

I could definitly live with 2%. But 5% is too much not to say 10%.

[BombaUcigasa]

-a 3

[cschmitz]

One 400Mhash miner got 10% stale the last 2h. Any idea or suggestion why its 0.2% at deepbit with the same miners if its client side?  Never had so high rates so far and I've been through 5 pools now.

10% is also the Ballpark i have seen with my 3gh total miners, it was certainly alot higher than anything i have seen in other pools, i think i have enough experience in BTC mining to rule out that the error is on my side.

[rb1205]

Just to explain why oldtimer thinks it's fun:

Rejected shares are mostly a problem on the client side, not the pool side. And 2% is excellent, by the way.

From the stats page at bitcoins.lc

Valid shares for current round    1 482 761
Shares for current round    1 566 072

that's 6.94% overall stale ratio. It doesn't look like a client side problem to me.

[PabloW]

We need more hashrate to the pool. This is so slowwwwwwwwwwwwwwwwwww

[Meman]

"Instant payout requires your verified funds balance to be over 0.01 BTC. However we recommend waiting until 1 BTC minimum due to transaction fees."

Why do you pay transaction fees? Aint they optional? How much are they? 0,01 BTC each payout?

[Jarredm]

Hey Jine,

I would like to join your pool but my setup currently requires that I can configure my workers credentials.  I've been on slush but I like the smaller pools for some reason.  Feels campy!  Anyway, I need to config the credentials to make the common script work that I launch my miners with. While I could do a lookup for my computer's name I would then have the problem of not knowing which worker was down by looking at the site.  I am no expert but I suspect that allowing this config could attract more miners.

[kicaii]

I'm pointing my 1450 Mh/s at your pool. Hope this will help.

[PabloW]

hey Jine can you make a signature for forums? to show how many Mhash we are doing on the pool hehe

[UnluckyMiner]

I am new to pool mining (your pool is my first) -- Last night I allocated 2Ghash/s, but I am seeing a behavior which doesn't entirely make sense to me. Should my shares value able to go down? This is to say -- both values in the shares column shown for my worker (xxx / xxx) appear to rise and fall frequently.

I was under the impression the values in the shares column represented the total number of work units submitted and requested by my miner. Is this a value displayed to the user weighted percentage of the pool capacity? What does this value actually represent?

Any information would be appreciated. Thanks!

P.S. Happy IPv6 Day!

[PabloW]

I am new to pool mining (your pool is my first) -- Last night I allocated 2Ghash/s, but I am seeing a behavior which doesn't entirely make sense to me. Should my shares value able to go down? This is to say -- both values in the shares column shown for my worker (xxx / xxx) appear to rise and fall frequently.

I was under the impression the values in the shares column represented the total number of work units submitted and requested by my miner. Is this a value displayed to the user weighted percentage of the pool capacity? What does this value actually represent?

Any information would be appreciated. Thanks!

P.S. Happy IPv6 Day!

It shows the estimated shared from the last 30 minutes, thats why. Its been asked before too.

We're losing hash rate =/

[asfas16123]

It has to be implemented that you can choose your worker logins (not only comment on it), like you can on the other pools. It is totally inconvenient for people with 10+ gpus like it is. you actually named the username/passwords as a feature in this post, it is a really bad idea. I want my workers to have all the same password and be able to give them login names like nickname_1_0, nickname_1_1, nickname_2_0, nickname_2_2 for 2 rigs with 2 gpus each

Also the stale-share rate has to be fixed, I think this is the reason while most people stick with deepbit. If you have 5% less stale shares who cares about their 3% fee.

[rb2k]

After letting my 60 mhashes/s client work for a few hours, I still see the Unverified funds at 0.00000000 BTC.
I know it's not much of a hashing power, but shouldn't it at least have given me something?

[Jine]

http://bitcoins.wikispaces.com/FAQ

Please read regarding funds.

[rb2k]

ok, so I guess the answer would be: no block has been solved in the meantime.

[neptop]

Yep!
Current round duration: 1 day, 4 hours

[Jine]

We're extremely unlucky this round.