Skip to content

Improve coin selection guidance #1175

@yashrajd

Description

@yashrajd

Describe your content request

Hello, I would like to see improved guidance for (manual) coin selection.

Link to the page

https://bitcoin.design/guide/how-it-works/coin-selection/

Why would you like to change the content?
If you're requesting a change to existing content, please describe concisely why you would like to change it?

  • coin selection can be a sensitive matter in terms of privacy as well as fees
  • manual coin selection can be difficult thing for the user because 1) user may have several coins in their wallet 2) there can be a large number of ways to select coins (depending on a number of factors) 2) various coins can have different/arbitrary a) value b) other relevant properties & metadata c) anonymity set with d) previous linkages
  • this means the user must optimise/goal-seek for total value, fees as well as privacy, with a large number of possible choices and lots of information to deal with.

This seems to be an open & difficult problem, with no established solutions, and most (all?) applications simply default to a list of coins/addresses with little to no information around it.

The best/unique approach I personally have seen so far is nunchuk (screenshots below), and we should take it into consideration for guidance.

This is an interesting and open UX problem that I face frequently, and imagine more other users face as well.

This is a great opportunity for design solutions/guidance that improve UX while empowering the user to be improve their privacy!

Suggestions
If you have a concrete suggestion on how to change/add the content, write it up here

  • devise/discover/document at least couple of approaches to this beyond simply throwing a list of addresses/coins
  • make mockups for them
  • improve existing page

Additional context

  • Some new wallet projects might also be working on this
  • a related view inside applications is the address list view, perhaps that can be improved in conjunction with this.

Content guidelines
If you're a contributor looking to tackle the issue, you can preview our content guidelines.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions