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

[Jack of Diamonds]

34,560,000,000,000,000 hashes

I don't have access to MatLab either now, but that looks about right without any tools necessary.

This hypothetical round (that never occurred & the admins corrected it as being three different rounds), however, went as far as 9.6 million shares.

I know the subject is difficult for new miners though. There is a site with the old-type calculator that will show timeframes for block finding. Feel free to tinker with it
http://www.alloscomp.com/bitcoin/old_calculator.php

(Note that it works in khash not mhash like their new one, so for the hashrate of Bitcoins.lc, you would have to enter 600000000).

As you can see, the 95th percentile already occurs at slightly after 9 hours.
This round went past 99.999% @ 600,000,000,000 hashes per second after 19 hours

p.s. This round did not actually happen, the administrators corrected the error. Nor has a 9+ million share round ever occurred on any pool as of today. Deepbit has had 5-6 million share rounds, bitcoins.lc and slush have had similar, but that's about it.

[1713528783]

1713528783

[1713528783]

1713528783

[padrino]

Seeing all of this downtime with no apparent update on what's happening makes it hard to stay on the pool, I've been here from almost the beginning but maybe it's time to move.

[Jine]

Hi!

I'm sorry for the lack of updates - I've been really busy
We're about to launch a huge update for the underlying system, it will contain this (and more).

* Fully load-balanced bitcoind/pushpoold environment
 - Support unlimited amounts of nodes - we're starting with 3 tho.
 - Sticky connections so you always get connected to the same node

* Updates to our pushpoold which means less connections, less lag, less latency
 - Keep-alive fully supported now - all the way to you as a miner (bitcoind->pushpoold->gateway->your worker)
 - Issues with home routes etc dropping keep-alive after a couple of minutes is solved.

* Less stale shares then ever due to modifications on both pushpoold and bitcoind above.
 - Stats from my miner (currently): 1630 accepted - 8 rejected

* Company and name registered, for the upcoming exchange platform.
 - We're now "Bit LC" - http://www.bitlc.net will be the domain / name in the future
 - Stands for "Low Cost Bitcoin Services" - as it's exactly what we're planning to offer.

* The development on the exchange platform have started.
 - If you want, you can request features at our feedback page and/or at info@bitcoins.lc

EDIT2: Site related:

* We're implementing optional YubiKeys (2-factor authentication) in the new system.
 - This will mean extremely increased security for your bitcoins and you.
 - It will be impossible to do payouts, change payout address or similar without having the YubiKey with you.
 - It will be optional - you will still be able to access the site and do whatever you used to do, without getting one.
 - We're aiming at making it possible to use the same YubiKey with us - as MtGox sells for their service.

* We're will force all pages to HTTPS. Both using redirects and a HSTS policy:
 - http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
 - This is the same policy Paypal and a number of other big businesses enforces on their connections.

* And a lot more...

And yes - we will also launch the new site with API and everything else promised as soon as we're launched this.
We had to focus on getting the pool 101% stable before doing anything else, to avoid loosing our users, because you guys - are our first priority.

We have some other surprises for our loyal users as well, but more on that later.

By the way, some internal schematics of this huge project, it may not look much, but it's fully redundant and should be very, very scalable.
http://www.bitcoins.lc/assets/Bit_LC_Network.png - the configuration of pfSense + the network have taken over 8 hours in total to get it do were we are today.

We're working as fast as i can - please be patient and you'll see how awesome this will be.
Think of it as a mining pool on steroids (Quote from our IRC channel - #bitcoins.lc)

--
Regards, Jim

EDIT:
I totally forgot to mention that we're actually upgrading the hardware node to, a total of 32GB RAM is being added and another 3x300gb SAS 10k RPM drives to.

EDIT2:
Added site-related news to!

[Jack of Diamonds]

I'm seeing the positive change already, site estimate shows hashrate increase of ~15% and stays stable.

Will this old domain still work after you switch to the new one?

[Jine]

We have not launched the new system yet, only made a few changes to lower the load and make it more stable.

Regarding new neame:

Everything will be 301-redirected to the new domain when the time comes.
No need to change miners nor worker-settings. Same goes with the new cluster/load balance setup, miner settings will be the same.

The domain will of course redirect to the new one to

I forgot a couple of things related to the site as well, previous post updated!

[techwtf]

I noticed the Long Polling notify is about 10 sec(sometimes ~15 sec) slower than other pool? please fix it ASAP.

[jrussell]

Best pool ever, thanks Jine 

[padrino]

Are changes underway, reject rate went through the roof for me in the last 30 minutes or so...

[Jine]

We just launched our new infrastructure, which is a fully load-balanced environment with all those changes i promised in the previous post.

We did have some issues at 23:10 -> 00:00 GMT with nodes that overloaded, which turned out to be a real simple mistake - we forgot to edit nofiles (maximum of open files and sockets) in limit.conf.
Took a couple of minutes debugging until i found the issue, made last changes, patched pushpoold real fast and pushed everything live.

Here's some RRD-graphs about the traffic we're currently getting:
http://www.bitcoins.lc/images/rrd1.png
http://www.bitcoins.lc/images/rrd2.png

I hope it will grow a bit more during the night to!

I noticed the Long Polling notify is about 10 sec(sometimes ~15 sec) slower than other pool? please fix it ASAP.

Check now It should be a lot better.

Hopefully, we can focus on getting the exchange platform online now, and those features that i know you guys really want.
Shouldn't take to long either

--
Regards, Jim

[Jack of Diamonds]

Will your exchange platform include wire transfer withdrawals?

[nodemaster]

Anybody else out there unable to log in, not even getting an error message?

[Jine]

Will your exchange platform include wire transfer withdrawals?

Yes.

Anybody else out there unable to log in, not even getting an error message?

Sorry about that, seems to be a security mesurement that gone haywire.
It's fixed now. (It banned IP's when they started to appear on multiple accounts, and then it mistakenly banned 172.16.0.254 - which is our gateway)

[nodemaster]

Sorry about that, seems to be a security mesurement that gone haywire.
It's fixed now. (It banned IP's when they started to appear on multiple accounts, and then it mistakenly banned 172.16.0.254 - which is our gateway)

Thanks for addressing this. I'm able to log in now. But unfortunately I now get an Internal Server Error while trying to withdraw BTC :-(

[joker]

Sorry about that, seems to be a security mesurement that gone haywire.
It's fixed now. (It banned IP's when they started to appear on multiple accounts, and then it mistakenly banned 172.16.0.254 - which is our gateway)

Thanks for addressing this. I'm able to log in now. But unfortunately I now get an Internal Server Error while trying to withdraw BTC :-(

I can't withdraw either. I don't get an error just a plain white page.

[Jine]

Thanks both for noticing.
The issue was we runned out of inodes (maximum amount of files on the system) due to a issue with php-fpm+cron.

I permanently solved it and moved the sessionstorage to memcache.
Sorry for these issues last days. Hopefully everything will work flawless after this.

Payouts should work now to.

[Stocker]

Hey, I did a payout and it went through and is posted on the site but no transaction listed in my client and no coins. Any help would be great.

Thanks

[Jine]

The issue with payouts that many seems to not understand is that your client/wallet need the full blockchain to be able to "see" the transaction.
If you're using the default GUI-client, at the bottom of the main window you'll see a line saying "Block: xxxxxx".

That block needs to be close to the same reported at by bitcoinwatch.com or similar

Without you having the blockchain it will not show up in the client, and you'll not see any coins.
If the transaction to show up on blockexplorer (could be delayed up to 10min) it exists on the bitcoin network and there is not much we can do about it.

Please ask in the other forums if you're having problems with the client and getting the blockchain.

Thanks!

/ Jim

[Stocker]

Gotcha, thanks for the reply!

[m3ta]

I'm not going to be a b%tch, but lets face it - is Deepbit's UI good? Are their fee OK? Is it professional enough? - No, not even close.

Having something "Current offline due to database work." 24/7 as you have is hardly professional, thus not giving you the right to comment on anyone else's professionalism.

[Jine]

We do have a code freeze in the production environment.
Nothing unless it's critical gets pushed live.

This is due to the upcoming new release, new platform and new build of the site.

I could change that message tho, but i rather focus on developing instead...