Bringing this one back…
In Oxford, there are now 3 baker parameters stored in the context: consensus key, limit_of_staking_over_baking and edge_of_baking_over_staking.
Let’s add a 4th parameter, rewards_destination, as described in the original post? Assuming Adaptive Issuance activates, this will only direct rewards from delegation, not rewards from staking which will be handled in-protocol.
The arguments I initially brought up still apply. Plus:
Adaptive Issuance is great for bakers because they no longer have to run a third party software to pay rewards from staking. But they still have to pay out rewards from delegation with a third-party software.
They might just stop doing that and instead, opt for being a staking-only baker. But we’d lose an important facet of tezos governance in the proces, if this happens.
rewards_destination makes public baking easier, removing the requirement to periodically move funds from the offline baking address to a hot third wallet used for payouts from delegation.
The easier baking is, the less likely people will stop paying rewards from delegation.
