You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand correctly, you have been participating in a collaborative transaction with a low fee value that needs longer to confirm? That is an unfortunate scenario and can be prevented once JoinMarket-Org/joinmarket-clientserver#721 (JoinMarket-Org/joinmarket-clientserver#1602) is implemented. Till then, the only things you can do is 1) wait or 2) CPFP the transaction.
If I understand correctly, you have been participating in a collaborative transaction with a low fee value that needs longer to confirm? That is an unfortunate scenario and can be prevented once JoinMarket-Org/joinmarket-clientserver#721 (JoinMarket-Org/joinmarket-clientserver#1602) is implemented. Till then, the only things you can do is 1) wait or 2) CPFP the transaction.
Hope this helps.
Thank you for the information, when will this be implemented or estimated implementation time? Also I’ve only done CPFP through sparrow, what’s the best way to do it through Jam? On mempool or something else?
Thank you for the information, when will this be implemented or estimated implementation time?
As far as I am aware: No, there is no estimate. Providing feedback on the linked issue is always a good idea and signals open source developers that there is interest in certain features. I am sure the devs will appreciate any and all feedback. 🙏
Also I’ve only done CPFP through sparrow, what’s the best way to do it through Jam? On mempool or something else?
To do a CPFP transaction you have to freeze all other UTXOs in the Jar and do a sweep (using only the one unconfirmed output) with a high enough fee for the miners to pick it up. However, if you are not in a hurry, you can always wait for the TX to confirm naturally or for someone else to CPFP.
Expected behavior
My Jar, due to fee amount should not have been selected for a smaller transaction where other participants easily filled the needs
Actual behavior
My Jar was picked before other participants with lower fees that could easily service the smaller denomination
Steps to reproduce the problem
Could provide UXTO as it currently says it won’t be processed anytime soon
Specifications
Additional context
How long can that UXTO be held hostage by a non priority sats/byte fee for miners?
The text was updated successfully, but these errors were encountered: