@pool operators using PoolserverJ,
Here is a feature request, i'am interested in and would like to hear your thoughts about it and if you think of using it too:
https://bitbucket.org/shadders/bitcoin-poolserverj/issue/12/estimated-block-reward-for-each-individualIn order to be capable as a pool operator to reward all pool member for block rewards, sooner or later transactions fees should be considered.
As the lifecycle of BItcoin and other forks continue, transaction fees on top of the block reward become more and more important.
Feature Request: Add the possibility to insert the block reward + transaction fees in a custom field in the share table for bitcoin and other forks (just like our_result_bitcoin, our_result_namecoin today).
The information should be match to the time, when the share was submitted.
The fees per block could be extracted from the merkle root (as far as i understood) or via the rpc command getmemorypool (which could result in a new bottleneck if performed for each share).
Here is shadders comment:
This should be fairly trivial to implement as the current block reward / tx fees are already calculated by the workmaker.
There is a question to resolve in what to do about aux chains. These will also have rewards + fees. This can be added as well but given the arbitrary number and unknown names of future block chains would have to be implemented in a similar way our_result_chainname.
Also important to note that the tx fees recorded at the time of share submission probably won't be the tx fees of the final block when it is found.
This could be useful if you want to credit your miner the right value per share, when the share was submitted.
For pps pools it will become more and more difficult how to credit a share if block reward will cut in a half multiple times in future. Same goes for other payout methods like DGM.