Mitigate issues regarding high transaction fee rates #10676
Comments
|
Can you add #10678 to "Client-side improvements"? |
|
Pull requests for "monitor fee estimate history": |
|
@BTCparadigm This should be added to the list too - https://github.com/zkSNACKs/MaintenanceVault/issues/260, one thing not done yet there is monitoring mempool.space fee estimation history. |
This was referenced May 16, 2023
Closed
|
closing in favor of the board https://github.com/orgs/zkSNACKs/projects/26 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A compilation of tasks for improving our ability to manage mempool congestion.
Server-side improvements:
Improve backend mempool - @lontivero @molnard
Improve transaction fee estimation - @kristapsk @BTCparadigm
Improve fee estimation #9578Details
As discussed with @kristapsk, it's too risky to do this without long period of monitoring and comparison first. Instead, we should focus on improving and monitoring our current fee estimator and add sanity checks.Fee estimations based on current mempool observation #9792Details
As discussed with @kristapsk, it's too risky to do this without long period of monitoring and comparison first. Instead, we should focus on improving and monitoring our current fee estimator and add sanity checks.Mimic mempool.space fee estimator #10614Details
As discussed with @kristapsk, it's too risky to do this without long period of monitoring and comparison first. Instead, we should focus on improving and monitoring our current fee estimator and add sanity checks.Responsive fee estimation #10638Details
As discussed with @kristapsk, it's too risky to do this without long period of monitoring and comparison first. Instead, we should focus on improving and monitoring our current fee estimator and add sanity checks.maxmempoolandmempoolminfeezkSNACKs/zbx-bitcoin#2Client-side improvements:
Improve minimum input and output limit - @turbolay @adamPetho
Add maxfeerate to coinjoin configuration - @turbolay @adamPetho
Safety coinjoins - @turbolay @adamPetho
Safety Coinjoins #10567Details
Discussed with Clement and we deemed this one too nuanced or controversial to rush in to the next release.Load Balancing Coinjoins - @turbolay @adamPetho
Load Balancing Coinjoins, Randomly Skipping Rounds #10678Details
As discussed in 17.5.2023 Round Robin call, this is not that urgent.Improve coin selection - @turbolay @adamPetho
Toggle option: "Wait for funds to confirm before starting a new coinjoin" #10320Details
Controversial and needs more research.Register relatively more inputs in low fee environments #10681Details
Discussed with Clement and we deemed this one too nuanced or controversial to rush in to the next release.The text was updated successfully, but these errors were encountered: