I saw a reply now, and I think it makes sense.
P2pool connects to digibyted daemon and gets its work from there.
So if the dgb daemon is updated, the workload should be reflected to p2pool network too.
Maybe I am mistaking.
hmm.. Even though i really want that response to be true.
I'm also hoping that someone more credible might look into it.
The account that responded has no development background, has only 'forked' a repo or two and has been reg. on GitHub only for a few weeks.
That comment does ring true to me. I think the line for reward in networks.py is used as a sanity check
Like I say, I'm no pool expert but I did look into it more. Our reward code works very similarly to how the WorldCoin reward code and there was only one small change that was made in any of the working worldcoin p2ppool code I could find.
https://github.com/Rav3nPL/p2pool-rav/blob/a8ac1d6ebe68d7565e34b58e6e30a002f99a0812/p2pool/bitcoin/networks.py#L920
according to the changes made to the world coin code it should be switched to
Code:
SUBSIDY_FUNC=lambda height: 8000*100000000,
Sounds good.. I checked leaf too (crazy random blocks) and its the same.
Commented a min ago.. https://github.com/Rav3nPL/p2pool-rav/issues/57
In that case. the p2pool network is safe & ready! So, i'll just remove the block halving code and send a pull request to Rav
Thanks xplooited
pull request: https://github.com/Rav3nPL/p2pool-rav/pull/59
As soon as it is pulled. I'll try my best to let all the p2pool operators know.
Magic Update code:
Code:
git pull origin master
