Mempool congestion on Stacks: observations and next steps from Hiro

A new version of the Hiro Wallet extension (v2.16.0) is now available that supports manual fee configuration both for new transactions and existing ones that remain pending via “replace by fee” (RBF).

This version has been approved by the Firefox store already, so if you’ve installed it from there, it should update automatically soon if it hasn’t already. The version is pending approval for the Chrome store and should update automatically there soon as well.

If you are a Chrome or Brave user who needs this version before store approval, you can install it from source.

Please see the following instructions about how to use this new functionality once you’ve upgraded: How do I edit the fee and nonce values for transactions?

If you are a developer with contracts that have been failing to confirm reliably on the network, we encourage you to upgrade to the latest version of the Connect library (v6.1.0 or v12.0.0 if you’re using connect-react).

This version will allow you to pass a custom “fee” value during hand-off for transaction signing, which will be used to overwrite the default fee for users to execute your contract. We encourage you to pass a fee value that you believe will help these transactions settle on the network reliably given recent network usage trends.

This will save your users from having to realize themselves that a different fee is needed and to take steps to modify the fee manually, ensuring that a higher percentage of them broadcast transactions that settle quickly upon first attempt.

We will be working in the coming weeks to improve the UX around fee configuration even further. This is just a first set of steps to alleviate the most urgent issues with fees and transaction settlement. For example, we hope to provide users with useful fee recommendations (slow, medium and fast values) based on current network trends and the computational needs of their transactions.

2 Likes