The currently used minimumFee is only enough to not get purged from the mempools with default settings and results in transactions stuck for days.
Proposing to use the hourFee instead which is the estimate to aim for a confirmation within the next 3 blocks. This would be a more realistic timeline but still tries to save some without increasing the complexity of the order flow.
The mempool.space API returns 5 types of fee estimation values:
The currently used minimumFee is only enough to not get purged from the mempools with default settings and results in transactions stuck for days. Proposing to use the hourFee instead which is the estimate to aim for a confirmation within the next 3 blocks. This would be a more realistic timeline but still tries to save some without increasing the complexity of the order flow.
See my comment also on: https://stacker.news/items/171335