Quote from: eleuthria on January 06, 2014, 04:29:13 AM

Quote from: opentoe on January 06, 2014, 04:17:57 AM

I'm glad other people can spot when the pool isn't doing it's job. If no one caught onto this, would this just be buried by time? I guess I'm glad I don't understand the hard technical stuff, cause I'd be looking for holes all the time and would probably be spotting them all the time. I guess it's like taking money from a blind person. Who monitors the monitor?

Not doing it's job, but not working %100 I guess.

It's extremely rare since all of the bitcoind's on the various pool servers are connected to the payment server, so the odds of the payment server seeing a competing block before a Guild block are *very* low (less than 1 in 10 orphans). When they are missed, it's generally corrected a few hours later manually without anybody noticing, but it does take a few hours because correcting it is a manual process, including the detection that it happened in the first place. Bitcoind does not report orphaned blocks via any RPC commands if they were not originally accepted.

The current project for the pool is a complete ground-up rewrite of the Stratum code to make it more scalable (full utilization of many-core systems), allow for better merged mining integration (instead of the fairly limited version currently implemented), and multiple chains (for an scrypt multipool).

Part of this rewrite is also going to make the pool servers insert found blocks directly to the database, and then the payout server will check against them before awards are assigned. It won't prevent them from still needing manual intervention to get them paid (as a security/sanity check), but it will make sure they're properly logged at the time they're found and identified as not yet paid out in the Pool Stats page.

Can't you just program an exception report and post that? I'm sure you are human and maybe have missed some yourself, no?