I really appreciate you asking about this, as I asked about this feature as well. It was decided to drop the current merge_maturity functionality (merging maturity directly into staked ICP), and to reconsider at a later time. There is a 4th option you didn’t mention: staking staked maturity as ICP in order to “lock-in” the current discount.
If you draw out the box of possibilities, it naturally leads to a family of related options:
-
exchange_maturity: maturity → staked maturity + staked ICP → liquid ICP -
stake_maturity: maturity → staked maturity -
disburse_maturity: maturity → liquid ICP -
not in this proposal (was
merge_maturity): maturity → staked ICP - not in this proposal: staked maturity → staked ICP
One issue with permitting “all that is logically possible” are the ways in which it adds more detail to the UI and documentation. But I will bring up your question again, especially since it came up in the first response!