BTC PoW Lab Pool — Hybrid Solo accounting and accepted-work telemetry

Hi OSMU, I am Carlos Monzon from Power CM Software. Disclosure first: I operate BTC PoW Lab Pool.

I would like to introduce our Bitcoin pool and invite technical feedback on how we explain accepted work and reward accounting to home miners.

Our Hybrid Solo model allocates a found block reward as 85% to the finder, 10% to Community Reward and 5% to BTC PoW Lab. Community eligibility uses accepted work within a rolling seven-day window; the finder is excluded from the Community Reward for their own block. This is a conditional allocation when a block is found, not a promise of periodic income.

One measurement detail matters with Vardiff: raw share counts alone are not comparable when difficulty changes. For example, 100 accepted shares at difficulty 1 and 10 at difficulty 10 have the same summed share difficulty. That is an illustration of accounting weight, not a claim about actual pool results or a guarantee of finding a block. Hashrate estimates also need the same observation window.

Pool status and telemetry

Research Lab

Which telemetry checks do you find most useful when evaluating a pool with a small ASIC? I welcome questions about the accounting model and anything in our presentation that is unclear.

Do you have the source code open sourced ?

Hi WantClue,

Thank you for asking. The production pool code is not currently published as an open-source release.

We publish the reward rules, public telemetry and verification data, but those should not be confused with access to the pool’s source code.

The Proof Center is here:

We also have a separate public repository for Share Work Audit, our accepted-work hashrate auditing tool:

That tool is not the pool engine. I want to be clear about that distinction so readers can assess exactly what is available for independent review.

Best regards,
Carlos Monzon
Power CM Software / BTC PoW Lab