bit pit - (LP, ESMPPS, 8-decimal payout, SSL, API, 0% fee, Almost 0% Stales!)

[hugolp]

Ive pointed 1 of my miners to your pool to try it out. Right now is working fine, not even one stale. If this continue this way, when you find the current block Ill point the other 3 as well.

Thanks!
We would appreciate your other 3 miners as well, that would definitely help use increase our hash rate.

Im very impressed until now. How do you do it to get so few stales? This should be a top pool.

[luffy]

@admin:
in order to make visible the very low stales plz add something like that in statistics:
Shares this round:   xxxxxx  (% of stale shares)

[Boing7898]

Ive pointed 1 of my miners to your pool to try it out. Right now is working fine, not even one stale. If this continue this way, when you find the current block Ill point the other 3 as well.

Thanks!
We would appreciate your other 3 miners as well, that would definitely help use increase our hash rate.

Im very impressed until now. How do you do it to get so few stales? This should be a top pool.

1bitc0inplz coded on his own the pool software, thats how we get 0 stales
Yeah, but we don't have enough hash rate to get in top 10 either..

[hugolp]

Im very impressed until now. How do you do it to get so few stales? This should be a top pool.

1bitc0inplz coded on his own the pool software, thats how we get 0 stales
Yeah, but we don't have enough hash rate to get in top 10 either..

Yes, I know, what I meant is that I am surpirsed that more miners did not jump in. No fees and almost no stales? What else can anyone ask? And with 10 or 20 "normal" miners moving in your could get 200GH/s and then it would probably snowball. Do you think the system would scale with higher loads? (You probably are going to say YES! but lets hear it).

[Boing7898]

Im very impressed until now. How do you do it to get so few stales? This should be a top pool.

1bitc0inplz coded on his own the pool software, thats how we get 0 stales
Yeah, but we don't have enough hash rate to get in top 10 either..

Yes, I know, what I meant is that I am surpirsed that more miners did not jump in. No fees and almost no stales? What else can anyone ask? And with 10 or 20 "normal" miners moving in your could get 200GH/s and then it would probably snowball. Do you think the system would scale with higher loads? (You probably are going to say YES! but lets hear it).

What you mean with scale? You mean balance the load of all the new miners? Well, you must ask 1bitc0inplz for that
But since we are running on a powerful dedicated server, I think we can 

[1bitc0inplz]

Thanks all, we appreciate your support.

Yes, we did write our own custom stack. We feel that this is one of the main reasons our stale shares are much lower than anybody else's.

Will it scale?

Undoubtably there will be the point where we hit a wall of some type. The question is, how can we scale past that issue. Right now current research indicates that pools hit scaling issues at the 350-450 GH/s, at which point they hit the limit that a single instance of bitcoind can handle. Considering this is the only piece of our stack we didn't write ourselves, this is highly likely also a wall for us.

However, that being said, we've already made some architectural choices that should allow us to scale past this without issues. We are even investigating how to remove bitcoind entirely from the equation, or at the least remove the burden of inter-process communication with it.

Keep up the great work everybody. This current round is a tough one, but probability is quickly shifting in our favor 

[Boing7898]

Keep up the great work everybody. This current round is a tough one, but probability is quickly shifting in our favor 

Round duration:   8 days, 6 hours, 12 minutes, 34 seconds

ç______ç

[lebuen]

I'm all in... switched to poclbm which has integrated failover, so no more need for the mining proxy. Absolutely stable and stale rate near to 0%.

Absolutely the best pool for me so far! Now I just hope that this very long current round is going to be over soon.

[Boing7898]

I'm all in... switched to poclbm which has integrated failover, so no more need for the mining proxy. Absolutely stable and stale rate near to 0%.

Absolutely the best pool for me so far! Now I just hope that this very long current round is going to be over soon.

Thanks for joining! Just for curiosity, what's your hashrate?

[lebuen]

1.5 GH/s - btw, why does your signature say "mining at EclipseMC"?

[Boing7898]

1.5 GH/s - btw, why does your signature say "mining at EclipseMC"?

Shit.. I thought I edited that but it seems I didn't.
I was mining at EclipseMC but I was getting too much stales and the admin wasn't very active. I really like 1bitc0inplz

[josephholsten]

I'm all in... switched to poclbm which has integrated failover, so no more need for the mining proxy.

I'm sorry you've needed failover. Since we've opened the pool, we've kept 99.84% uptime. That's may strike you as good reliability, but I know we can do better. Over half of that time was spent in our last major deploy on June 12, when we switched to a system that lets us hot deploy with no downtime. Since then we've kept 99.93% uptime, with only one bad deploy taking us down for 12m on June 18.

We've just started tracking response time as well, so I'm looking forward to telling you about that in a month or so.

[1bitc0inplz]

I'm all in... switched to poclbm which has integrated failover, so no more need for the mining proxy. Absolutely stable and stale rate near to 0%.

Absolutely the best pool for me so far! Now I just hope that this very long current round is going to be over soon.

Thank you very much.

We are still working on the mining proxy bug. Just for the sake of explaining everything, this is actually the intersection of two bugs. One bug in PHP (which is what the proxy is written in) and one bug in Node.js (which is what our pool is written in). Apparently PHP sends an erroneous CRLF on HTTP POSTs, which is against the spec. Apparently, also, Node.js refuses to process such a request.

This bug in Node.js has been documented here: https://github.com/joyent/node/issues/1165

We are still unsure how we can best resolve this until Node.js (or PHP) fix their respective bugs, but we are still investigating options.

Sorry it took so long, but I am glad to hear that you found another way to achieve failover.

[1bitc0inplz]

We've just started tracking response time as well, so I'm looking forward to telling you about that in a month or so.

Welcome Joe!

For the purpose of validating him, I would like to introduce everyone to the 3rd (and final) member of bitp.it.   

[1bitc0inplz]

Just a quick update everyone. We just did an update to the site and have a couple of goodies for everyone.

Firstly, we've reworked our entire hash rate estimation and we feel that this will provide a much more accurate hash rate estimation for everyone. Let us know this is working for you.

And, most noticeably, we've added a global stats bar to the top of the website (including the homepage). This status bar auto-refreshes approximately every minute, so if you're anything like me you can see if we've solved our next block yet without constantly hitting refresh on your browser 

[Boing7898]

And, most noticeably, we've added a global stats bar to the top of the website (including the homepage). This status bar auto-refreshes approximately every minute, so if you're anything like me you can see if we've solved our next block yet without constantly hitting refresh on your browser 

Love it 
Now guests can see the hash rate too! Nice!
P.S: Thanks for the article review! I still have to add a lot of things

[lebuen]

Very satisified so far, we also should be around the 95%-percentile so it shouldn't be too long before a block is found. Stats bar looks nice. Just one question: why do you display "score" in the dashboard? are you using prop or score at the moment?

[lowentropy]

Very satisified so far, we also should be around the 95%-percentile so it shouldn't be too long before a block is found. Stats bar looks nice. Just one question: why do you display "score" in the dashboard? are you using prop or score at the moment?

We used to do scoring, so it's kind of a hold-over. Right now what this displays is your % of the top contributor. So the top guy on the leaderboard has a score of 100, if you have half his shares you have 50, etc. I'm not sure it's really useful anymore 

[lowentropy]

I'm really tired of this round

So i'm offering a 5 BTC bounty to whoever can kill it. With extreme prejudice. 

[jme621]

i think the hashrate thing is broke, it says my miners are only doing 49mh total, not the 1.25gh they are really doing