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

gui: Generate bech32 addresses by default #15711

Merged
merged 1 commit into from Apr 8, 2019

Conversation

Projects
None yet
6 participants
@MarcoFalke
Copy link
Member

commented Mar 31, 2019

Most services support bech32 addresses now, so generating legacy addresses by default seems overly cautious. bech32 addresses are more robust and user friendly in multiple ways.

@promag

This comment has been minimized.

Copy link
Member

commented Apr 1, 2019

utACK faf62d9, maybe add a release note "checkbox changed, but the behavior/outcome remains the same".

@MarcoFalke

This comment has been minimized.

Copy link
Member Author

commented Apr 1, 2019

Good point, but I think for the GUI it is self-explanatory, since the button comes with a help text and a massive tooltip

@laanwj

This comment has been minimized.

Copy link
Member

commented Apr 2, 2019

utACK faf62d9, don't think a release note is needed for this specifically, though a general release note on switching to bech32 by default would make sense

@fanquake

This comment has been minimized.

Copy link
Member

commented Apr 3, 2019

tACK faf62d9

bech32

legacy

@MarcoFalke MarcoFalke added this to the 0.19.0 milestone Apr 4, 2019

@MarcoFalke

This comment has been minimized.

Copy link
Member Author

commented Apr 4, 2019

This will be merged next Monday unless there are objections

@Empact

This comment has been minimized.

Copy link
Member

commented Apr 5, 2019

utACK faf62d9

MarcoFalke added a commit to MarcoFalke/bitcoin that referenced this pull request Apr 8, 2019

Merge bitcoin#15711: gui: Generate bech32 addresses by default
faf62d9 gui: Generate bech32 addresses by default (MarcoFalke)

Pull request description:

  Most services support bech32 addresses now, so generating legacy addresses by default seems overly cautious. bech32 addresses are more robust and user friendly in multiple ways.

ACKs for commit faf62d:
  promag:
    utACK faf62d9, maybe add a release note "checkbox changed, but the behavior/outcome remains the same".
  laanwj:
    utACK faf62d9, don't think a release note is needed for this specifically, though a general release note on switching to bech32 by default would make sense
  fanquake:
    tACK faf62d9
  Empact:
    utACK bitcoin@faf62d9

Tree-SHA512: a03e6ccf1e5476fe800941992c531664830cec0644984d8bce97c8d8f5d6d9abd528ab979892368cd195e7c8b9083d6b8dfd36a7cb172aa9dbeaa01a948e30e1

@MarcoFalke MarcoFalke merged commit faf62d9 into bitcoin:master Apr 8, 2019

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@MarcoFalke MarcoFalke deleted the MarcoFalke:1904-guiBech32 branch Apr 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.