diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2019-04-08 10:21:41 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2019-04-08 10:21:46 -0400 |
| commit | 414d8461fd6779ccaa13a57e88220ffc33d8ec85 (patch) | |
| tree | c4a181812a72d6bb070d7f63321a786c526202bd /src/uint256.cpp | |
| parent | b4e74f938b753f87449e4f1bc64df197832e56b2 (diff) | |
| parent | faf62d9415d74e69356d2b64c134184814938708 (diff) | |
Merge #15711: gui: Generate bech32 addresses by default
faf62d9415 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 faf62d9415d74e69356d2b64c134184814938708, 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 https://github.com/bitcoin/bitcoin/pull/15711/commits/faf62d9415d74e69356d2b64c134184814938708
Tree-SHA512: a03e6ccf1e5476fe800941992c531664830cec0644984d8bce97c8d8f5d6d9abd528ab979892368cd195e7c8b9083d6b8dfd36a7cb172aa9dbeaa01a948e30e1
Diffstat (limited to 'src/uint256.cpp')
0 files changed, 0 insertions, 0 deletions