Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 51. (Read 903150 times)

AFAIK, it seems Michael believes that it would spread from NY and I guess that's why he's looking at shutdown scenarios but I agree that just because something passes in NY is no reason to close the pool.

how is NYC going to do anything about a pool hosted in a different state

Thanks. That makes sense now


Thank you

NY is one of the least free states in the country, and NYC makes it a lot worse. that alone makes it a shit hole

Homer: New York is a hellhole. And you know how I feel about hellholes.

Obviously some hick who's never left his own state.

Under that scenario, the system would be partially hoppable, since if a shift finds 1 or 2 blocks early on, there's a greater than average chance of that shift ending up above expectation by the time it closes.  In shift-based PPLNS, you can't pay blocks to the shift that found them without opening up this hoppable factor.  In the long run, a hopper *would* end up ahead.

The shift doing the work "18727 in this case" is not paid, it is still growing in shares until it is "Completed". A shift that is still "In Progress" or doing "work" could find 10 blocks but it will not get any applied to it when it "Completes". Thus the 10 "Open Shifts" which are all "Completed". The first "Closed Shift" is not included in the "Luck Chart" because of the likely hood it "May" still have a "Pending Block Waiting for Confirmation". This is a pretty common occurrence. In this case, the first "Closed Shift 18717" was increased by one block, when Block 312297 was "Confirmed". Because it was "Open" when the block 312297 was found but had become the "First", "Closed Shift" before the block was "Confirmed". Thus leaving shift 18727 as the first "Open Shift" but with a Zero when the Block was Confirmed.

I can clearly see that. My concern is, shouldn't shift 18727 include any blocks found before its completion time?

Shift 18727 finished at 11:37 AM.  Block 312297 was found at 11:22 AM, before 18727 was complete.  So Block #312297 was not applied to Shift #18727, it was applied to 18726 (and the 9 before it as well).


EDIT/ADDED LATER: What you are probably noticing is that the block wasn't applied to 18726 (and the 9 before it) until after 18727 was finished.  This is probably because the block didn't have an extra confirmation yet.  The shifts a block is going to be paid to are determined when the block is FOUND, not when it has a 2nd confirmation.  This is why the most recently closed shift can occasionally get an extra block paid to it (and also why the luck graphs don't include the most recently closed shift).

Maybe a dumb question, but why shift #18727 shows 0 blocks found, when we have found block #312297 before that shift was closed? In which shift will be block #312297 included?

Thanks!

P.S. I know this is affecting only luck calculations for the pool, because I have already received the reward for the 312297 block.

It depends on my mood when you ask me.  I've enjoyed it mostly, though sometimes you get those days where you have a flood of emails from completely clueless people.  I'm terrible as a customer service person when the other side is missing a few nuts & bolts.  I'm more than happy to help and explain things to people under most circumstances, but only if the other side is listening.

I have put time into preparing more formal closure processes though, so I guess you can say I've been looking to retire from the pool business (even though that could be years away).  Being in this game since early 2011, I've seen a lot of Bitcoin businesses go bust, "get hacked", or walk away without notice.  I've always wanted to make sure that when BTC Guild eventually goes away (and it will SOMEDAY), it does so on a positive note.  

It's also no secret that I'm a pessimist when it comes to the future of mining centralization and the fate of public-only pools.  Part of that line of thinking has occasionally made me think of closing sooner rather than later, just because of the fact that if BTC Guild had any sort of compromise or payout error, the likelihood of recovery is significantly lower than it would have been last year (like when the 0.8 upgrade cost the pool [me] 1200 BTC).  While I doubt something like that would happen again (it certainly wouldn't be as big of a loss), it is a potential obstacle with ending on a positive note, and as such is a risk that I'm always factoring into my decisions.

Hey Eleuthria, are you/have you been looking to retire from the pool operating business?

As with any liberals, they attempt to over regulate under the guise of "to protect the starving Oompa Loompa children from pedophiliac dildo wielding alien invaders with the penchant for sodomy from Uranus – don’t you have any compassion?!!?"... Regardless of the nanny state's final solution, shutting down due to one state's asinine approach to this seems bit of an all or nothing approach. I understand the need for contingency plans, but I'm sure there is a more reasonable solution to this that can keep BTC Guild running.

I'm sure Eleuthria is actively brainstorming the options as we speak. A few ideas have beed floating around on the forums that may work...??

Simply ban NY IP addresses - Granted BTC people are tech savvy enough to VPN, but BTC Guild can't be held responsible for a users work around.

I can’t remember what the others were, and I've got to get back to work.. But last little tid bit would be I'm sure there are lawyers out there that would be interested in this type of issue that can be consulted with.

If your finest place regulations become cement then I think you should either leave that state or be banned from mining pools instead of the mining pools going offline.

Go ahead, bite the Big Apple.
Don't mind the maggots!

nyc is a shithole

The law would affect us all in NYS.
At least that is how it reads.

You can disagree with state legislation without insulting the entire state there, guy.

New York City happens to be the finest place I have ever lived and worked.

And yes, bloomberg's attempted soda ban was stupid.

Don't confuse New York City with the state of the same name. The soda-size ban was passed by the city but overturned by the state Supreme Court.

its been seven rounds without finding a block... seems like a lot...