> No pool should ever, ever, ever not track the total liabilities in each ecash epoch.
You are jumping to conclusions. The pool tracks liabilities with absolute precision. The value add for the pool is that expiring ecash forces users to exit their position and claim their rewards. This allows the pool to zero out their liabilities in a rolling time window fashion.
> actually building that is the hard part here
Free and open source software means I can build it once and give it away to the world for free.
Login to reply
Replies (2)
> You are jumping to conclusions. The pool tracks liabilities with absolute precision. The value add for the pool is that expiring ecash forces users to exit their position and claim their rewards. This allows the pool to zero out their liabilities in a rolling time window fashion.
This isn’t a unique feature of ecash. The pool could do this today if they wanted. Similarly they could not do it in an ecash system, if they want.
> FOSS means I can build this once
True, and to be clear I think this is something that should be built and would be great for the mining ecosystem unrelated to ecash! If miners start doing monitoring locally pools can track less things and that’s better for everyone. I’m still very skeptical that the last step of jumping to ecash-based shares is useful.
> they could not do it in an ecash system
Not sure I follow. This is possible and I am building it.
> I think this is something that should be built and would be great for the mining ecosystem unrelated to ecash! If miners start doing monitoring locally pools can track less things and that’s better for everyone.
Yes. It is orthogonal to eHash, (something you helped me realize :) but this is the tech we need to save bitcoin.
Nobody else has built it so I will build it. I'm gonna need help, tho.
I plan to elaborate at @btcplusplus in May.