Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Waste of previous BTC checkpoint transactions when new UTXOs are spent #175

Closed
gitferry opened this issue Jun 14, 2023 · 0 comments · Fixed by #176
Closed

Waste of previous BTC checkpoint transactions when new UTXOs are spent #175

gitferry opened this issue Jun 14, 2023 · 0 comments · Fixed by #176
Assignees
Labels
enhancement New feature or request

Comments

@gitferry
Copy link
Collaborator

This issue is brought up by @vitsalis as follows.

Lately BTC fees have become super volatile, leading to us having UTXOs stuck in the mempool. More particularly, the following scenario happens: we submit a transaction with a reasonable fee based on the estimation based on the current mempool. A lot of BTC transactions come along and they continuously raise the fees. Our transactions are stuck in the mempool and therefore unspent. Typically, we combatted this issue by having many available UTXOs, but this does not seem to be enough, as lately a transaction might get stuck in the mempool for weeks. Currently, on our testnet, we do not have any checkpoints for 4 days due to only having two available UTXOs both of which are stuck. Clearly, this is not maintainable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant