In particular, I think I read somewhere that it is in the planning to put an expiration on market order. I think this is required because of the pruning of transactions and this is different than with 2.0+.
Of course, adding expiration will require to set a new default value for the number of blocks before expiration happens. This default needs to be defined for each different transaction type that requires expiration.
Here below is a suggestion.
Add a new input parameter which would multiply ->
- the default number of blocks before expiration; and
- the default blockchain fee.
Such kind of new parameter to expiring transactions would be very much more convenient for the users, as they could pay and decide in advance for how long they wish “to rent data space” on the blockchain. Also, this could also significantly increase transaction fees to the forgers on the network.
I mean also that without such new input parameter, there will always be a complaint that expiration does not fit a user need.
What is the plan about this issue for 3.0+? Does another solution than the one described above is planned?
I hope the solution retains by Jelurida will be more convenient than the one that is currently provided for “leasing”.
Any other ideas about this issue is also welcome to be post below.