[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[fivejonnyfive]

A step in the right direction on the regulation front that jeopardizes the pool:

The Bitcoin Foundation has convinced, at the very least the NYDFS to extend the comment period on it's proposed regulation. The spit may still hit the fan, but at least it's rate of approach has been slowed. Submit your comments folks.

https://bitcoinfoundation.org/press-releases/press-release-august-6-2014-bitcoin-foundation-filing-with-n-y-department-of-financial-services-wins-promise-of-more-information-about-bitlicense-proposal/

[1714202547]

1714202547

[MoreBloodWine]

New Milestone for me, hit 4 BTC earned from the pool since I joined, whenever that was.

[ManeBjorn]

Congratulations!!
I just hit 10 BTC the other day.
I have 7 th/s going now I hope our luck streak keeps level. We have been having a good run again. 

New Milestone for me, hit 4 BTC earned from the pool since I joined, whenever that was.

[iglasses]

Earnings   13.49557721


I need my head examined...lol

[ManeBjorn]

It is fun mining I really love it.
I hope that he does not close the pool because if NY.  It is the best pool.  I will be lost without it.

Earnings   13.49557721


I need my head examined...lol

[Soros Shorts]

I've mined on this pool since the proportional payout days. I believe internet connectivity back then was through Comcast residential service. It would be a sad day to see it close down.

[iglasses]

WTF?

Any info on what pools this hit?

http://www.wired.com/2014/08/isp-bitcoin-theft/

[eleuthria]

I've mined on this pool since the proportional payout days. I believe internet connectivity back then was through Comcast residential service. It would be a sad day to see it close down.

It was Comcast business service, but it was very quickly moved to proper dedicated servers once the modem started crashing every 10 minutes after a few days .  The pool actually started out being hosted out of my dining room on one of the mining rigs that was mining on the pool.

[iglasses]

I've mined on this pool since the proportional payout days. I believe internet connectivity back then was through Comcast residential service. It would be a sad day to see it close down.

It was Comcast business service, but it was very quickly moved to proper dedicated servers once the modem started crashing every 10 minutes after a few days .  The pool actually started out being hosted out of my dining room on one of the mining rigs that was mining on the pool.

Eleuthria, did you get one of those 'special' letters?  lol those were the days!!

[MoreBloodWine]

I know I have my own way of tracking what I call true 24hr stats but I've NEVER seen it this bad on the site display.

24 Hour Earnings 0.04405548

Under new diff, should be seeing 0.081 a day, under old if I think it was 0.086.

[eleuthria]

I know I have my own way of tracking what I call true 24hr stats but I've NEVER seen it this bad on the site display.

24 Hour Earnings 0.04405548

Under new diff, should be seeing 0.081 a day, under old if I think it was 0.086.

That tends to happen when you have a 7 hour, 6 hour, and 5 hour block in the previous 24-hours of shifts.  75% of the 24-hours only solved 3 blocks.


Could be worse though.  Slush has had 2x > 24-hour blocks in the last few weeks.  0.00000000 for 24-hours would be terrifying.

[opentoe]

The United States makes it almost impossible for a tiny/small/medium company to run. Crypto or not. Move all servers to a country where they want our business and welcome us with open arms. Co-locate your mining rigs to the same. Eliminate the US completely and we'll all be fine. When you see such huge tax breaks for large corporations and small business just gets shit on you start to get that animosity that never goes away.

And yes, NYC is shithole. Last time I was there the smell alone made me want to leave as quick as possible. Just another over grown city bursting at the seams.

[MoreBloodWine]

I get what Stale / Dupe is but remind me about other, Ty.

[eleuthria]

I get what Stale / Dupe is but remind me about other, Ty.

Other is a catch-all for rare rejects which are almost always due to client-side errors.  Other contains 'Low Difficulty' and 'Unknown Work' rejects.  Low Difficulty will only happen if you don't set your miner difficulty and you just started mining (before vardiff has adjusted you), or if your software is screwed up.  Unknown work means you sent work that didn't come from the pool.  This will only be BTC Guild's fault if the servers were restarted (since they forget what work has been assigned), which hasn't happened in about 3 months and counting.  Unknown rejects can also be when you submit very old (and very stale) work for some reason.  The pool forgets about jobs from prior blocks after enough new work has been generated for the newest block.

LD - Only happens when first starting, and only if you don't set your difficulty.  Otherwise, client software error.
Unknown - Normally client side error, sometimes connection related (disconnected and reconnected to a different backend).

[MoreBloodWine]

I get what Stale / Dupe is but remind me about other, Ty.

Other is a catch-all for rare rejects which are almost always due to client-side errors.  Other contains 'Low Difficulty' and 'Unknown Work' rejects.  Low Difficulty will only happen if you don't set your miner difficulty and you just started mining (before vardiff has adjusted you), or if your software is screwed up.  Unknown work means you sent work that didn't come from the pool.  This will only be BTC Guild's fault if the servers were restarted (since they forget what work has been assigned), which hasn't happened in about 3 months and counting.  Unknown rejects can also be when you submit very old (and very stale) work for some reason.  The pool forgets about jobs from prior blocks after enough new work has been generated for the newest block.

LD - Only happens when first starting, and only if you don't set your difficulty.  Otherwise, client software error.
Unknown - Normally client side error, sometimes connection related (disconnected and reconnected to a different backend).

Ty for that, just brought up 4 S3's so I'm close to 5Th now mad up of 9 devices, on of which is a rPi with about 10g on it I use for fun.



It should settle more later as the S3's haven't been running long.

[eleuthria]

Some changes were made to the initial connection server to change how it caches bad workers.  Previously the bad worker list was cleaned up after every block, which caused that server to slow down a little after a new block hit.  This server is only used for the initial share submission, after which miners are redirected to different servers.  This process was updated to only expire bad workers after 1 hour, in order to stagger the clearing of the bad worker cache.  This should make the initial connection more responsive.  Most users shouldn't notice this, since you only talk to that server when first turning your miner on, or recovering from a disconnection.

[MoreBloodWine]

Some changes were made to the initial connection server to change how it caches bad workers.  Previously the bad worker list was cleaned up after every block, which caused that server to slow down a little after a new block hit.  This server is only used for the initial share submission, after which miners are redirected to different servers.  This process was updated to only expire bad workers after 1 hour, in order to stagger the clearing of the bad worker cache.  This should make the initial connection more responsive.  Most users shouldn't notice this, since you only talk to that server when first turning your miner on, or recovering from a disconnection.

Did this require any sort of reset ?

[eleuthria]

Some changes were made to the initial connection server to change how it caches bad workers.  Previously the bad worker list was cleaned up after every block, which caused that server to slow down a little after a new block hit.  This server is only used for the initial share submission, after which miners are redirected to different servers.  This process was updated to only expire bad workers after 1 hour, in order to stagger the clearing of the bad worker cache.  This should make the initial connection more responsive.  Most users shouldn't notice this, since you only talk to that server when first turning your miner on, or recovering from a disconnection.

Did this require any sort of reset ?

No, this only affected the initial connection server.  The only way a miner would've noticed this is if they turned their miner on at the exact moment I was doing the restarts.  Anybody that was already mining was no longer connected to that server.

[mstrongbow]

I know I have my own way of tracking what I call true 24hr stats but I've NEVER seen it this bad on the site display.

24 Hour Earnings 0.04405548

Under new diff, should be seeing 0.081 a day, under old if I think it was 0.086.

That tends to happen when you have a 7 hour, 6 hour, and 5 hour block in the previous 24-hours of shifts.  75% of the 24-hours only solved 3 blocks.


Could be worse though.  Slush has had 2x > 24-hour blocks in the last few weeks.  0.00000000 for 24-hours would be terrifying.

Every pool has their swings!
Slush has also had quite a few 10-20 block days in the past few weeks as well.
It is what it is yo...BTCGuild and Slush pools are the most reliable pools I have mined with.
Alsthough my primary pool is Slush pool, BTCGuild is my secondary (with a solo node in the works for my #3 backup)

[Billbags]

The Best choice eleuthria ever made was not putting a forum link on the dasboard of Guild. You actually have to read and search to find his forum. Thank You!!! Every thread right now is tracking deliveries of s3's and 400 pages of what power supply to buy. Anyway, the pools been doing good recently and was looking for any new info on the NY situation. I see it's been delayed for furthur discussion, I guess the Bitcoin Foundation along with others asked for more input to be made before final laws are made.