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

Already on GitHub? Sign in to your account

Adding "fee management" infos in the wallets section #1255

Closed
jlegoupil opened this Issue Mar 7, 2016 · 5 comments

Comments

Projects
None yet
6 participants

Add “fee management” information in the bitcoin.org wallet section along with the standard infos : "control over your money", "validation", "transparency", "environment" and "privacy".

It would help users know how wallets manage fees so they can make the best choice and avoid having stuck transactions due to poor fee handling from wallets. Speaking for myself, "fee handling" was a decisive parameter when I chose my wallets. This is even more the case now.

We can also expect wallet innovation in the "fee management" space in the coming months due to the deployment of Opt-in RBF which makes it even more relevant, imo.

Contributor

theymos commented Mar 7, 2016

This is a good idea IMO.

Contributor

Cobra-Bitcoin commented Mar 9, 2016

Great idea!

A proposal for "fee management" categories :

  • Vulnerable to delays (orange) : the fee is hard coded (also includes wallets that enable different hard-coded fees such as low/high priority).
  • Basic protection against delays (green) : user can manually set the fee or the wallet estimates a smart fee from the current mempool of unconfirmed transactions.
  • Full protection against delays (bold green) : user can increase the fee after broadcasting the transaction to the network (RBF enabled wallets)
Contributor

instagibbs commented Mar 20, 2016

@jlegoupil note that point #1 can also mean users are regularly over-paying in fees during slow times as well.

@wbnns wbnns self-assigned this Dec 9, 2016

@wbnns wbnns added the Under Review label Jan 31, 2017

Contributor

crwatkins commented Apr 24, 2017

The #1568 PR has been merged. I'll close this issue for now. Please feel free open a new issue for any updates to the current fee scoring. Thanks to @jlegoupil for the proposal.

@crwatkins crwatkins closed this Apr 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment