Change Details

The parameters are chosen so that pool can either: - Directly read the real time target value from the rtt.nexttarget field; - Or compute it locally by using the other rtt.* parameters. The nexttarget field is not using a compact form for the following reasons: - The pools can check the computed values against this output. Using the compact form will only make it possible to check that this is about correct due to rounding but makes it hard to check for exactness - The bits need to be unpacked anyway; so the cost is only on the blocktemplate json size which is an acceptable tradeoff wrt to the above mentioned benefit. More gains can be found in other places and most notably on the (needlessly) very verbose staking reward fields. Depends on D16729.

The parameters are chosen so that pool can either: - Directly read the real time target value from the rtt.nexttarget field; - Or compute it locally by using the other rtt.* parameters. Depends on D16729.

The parameters are chosen so that pool can either: - Directly read the real time target value from the rtt.nexttarget field; - Or compute it locally by using the other rtt.* parameters. The nexttarget field is not using a compact form for the following reasons: - The pools can check the computed values against this output. Using the compact form will only make it possible to check that this is about correct due to rounding but makes it hard to check for exactness - The bits need to be unpacked anyway; so the cost is only on the blocktemplate json size which is an acceptable tradeoff wrt to the above mentioned benefit. More gains can be found in other places and most notably on the (needlessly) very verbose staking reward fields. Depends on D16729.