I read that pages, but I don't understand what kind of "proof of work" we are talking about.
I mean: I'm interested in a "proof of correct work". This kind of proof needs not only to you, but to everyone is running this client.
My incentive is: I'm sure that I (and we all) are working in the correct way.
I know what you mean. We have no proof of correct work @ runtime. Even less so for every single key.
We have proof of correct work before generators are released. Then, we have "only" proof of work (done).
My question is: do you check in some way that my work is correct or you check only that I run your code without tampering? It is different.
It is. If your machine had e.g. faulty memory or a CPU/GPU that would exhibit faulty computations, your client would effectively pollute the "done"-db. Of course, your client would have to exhibit this behavior after the LBC -x run (which would have to run without errors).
For example incentive firework from SlarkBoy is good as a control system too. And money is not even necessary to perform this kind of control.
Do you have any mechanism in mind? We could issue periodic "LBC -x" runs for the extra paranoid.
We are searching for something extremely rare. So sentences like:
"I do trust the LBC codebase"
"anyone with attention deficit hyperactivity disorder would be in the wrong place here"
are not soothing to me

Probably I'm only frustrated, I would really be sorry if we don't hit #51

I think I am pretty well aware of the "rare event" problem. In fact, programming the LBC is like programming a spacecraft: After months of no events, you need it to do the right thing within seconds. I give you that "anyone with ADHD is in the wrong place here" is not soothing. Ok.
But "I trust the LBC codebase" should be.
We have still over 100 tn keys search space, so there is hope. We may also have already a FOUND.txt slumbering somewhere again and the operator slumbering too. There is still hope.

Time for frustration is tomorrow 11 a.m. UTC
Rico