My only concern with using it on the POBH side is it directly competes with PODC..
PODC combines coins into one for the updates, so only folks not working on PODC could participate in POG, this would need to be addressed somehow.
Yes, and just to clarify, I was thinking something like this could go down:
We release our testnet version in a week (or whatever), with the following:
POBH is extended to be POG(utilizing POBH), and the small miner reward (of 600~) is actually the source of what is distributed in the pool (IE 20% of 600 is 120 that goes to the reaper, the remaining 80% goes in the pool). PODC is left in an "ON" state.
We test for a couple months and fit this particular environment into our mandatory release.
So in Prod, POG is basically utilizing heat mining budgets.
Then when we feel safe, we do a hard cutover. (That is Disabling PODC and diverting its entire budget back into POG). I havent studied the possibility of doing a slow cutover. (I think the testing results + prod POG results would dictate a potential "cutover block" to remove PODC that could be fit into one single mandatory, if lucky - but this is definitely not something that I would rush).
I plan on putting extra metrics in testnet so we can reconcile every hash and bbp in the pool; this should make it easy to ensure the whole thing is square.