# Reward Account Selection for bakers **URL:** https://forum.tezosagora.org/t/reward-account-selection-for-bakers/4828 **Category:** Research and Development **Created:** [November 10, 2022, 8:51pm UTC](https://forum.tezosagora.org/t/reward-account-selection-for-bakers/4828 "2022-11-10T20:51:09Z") **Posts on this page:** 1 **Showing post:** 10
### Author: ![nicolasochem](https://forum.tezosagora.org/user_avatar/forum.tezosagora.org/nicolasochem/32/544_2.png) [@nicolasochem](https://forum.tezosagora.org/u/nicolasochem) #### Post date: [January 12, 2024, 6:50pm UTC](https://forum.tezosagora.org/t/reward-account-selection-for-bakers/4828/10 "2024-01-12T18:50:04Z")
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. --- _[View the full topic](https://forum.tezosagora.org/t/reward-account-selection-for-bakers/4828)._