-
Notifications
You must be signed in to change notification settings - Fork 37.9k
gui: Generate bech32 addresses by default (take 2, fixup) #16497
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
Conversation
Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK fa5a4cd.
|
||
if (model->wallet().getDefaultAddressType() == OutputType::BECH32) { | ||
ui->useLegacyAddress->setCheckState(Qt::Unchecked); | ||
if (model->node().isAddressTypeSet()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, to avoid nesting previous code you could do:
if (!model->node().isAddressTypeSet()) {
// Always fall back to bech32 in the gui
ui->useLegacyAddress->setCheckState(Qt::Unchecked);
} else if ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I will leave it as is for now, to not invalidate review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK fa5a4cd
fa5a4cd gui: Generate bech32 addresses by default (take 2, fixup) (MarcoFalke) Pull request description: This commit was missing from my previous pull request for some reason 🤔 : * gui: Generate bech32 addresses by default #15711 ACKs for top commit: jonasschnelli: Tested ACK fa5a4cd promag: ACK fa5a4cd. fanquake: ACK fa5a4cd Tree-SHA512: 4a38df929d7704bf08e50a2e814b2e6cd25c4165d040a84287045b44e32f4708750845520d64170ea58e41de3ca496da4625d3eb375f9528b21b364c22068a6b
…2, fixup) fa5a4cd gui: Generate bech32 addresses by default (take 2, fixup) (MarcoFalke) Pull request description: This commit was missing from my previous pull request for some reason 🤔 : * gui: Generate bech32 addresses by default bitcoin#15711 ACKs for top commit: jonasschnelli: Tested ACK fa5a4cd promag: ACK fa5a4cd. fanquake: ACK fa5a4cd Tree-SHA512: 4a38df929d7704bf08e50a2e814b2e6cd25c4165d040a84287045b44e32f4708750845520d64170ea58e41de3ca496da4625d3eb375f9528b21b364c22068a6b
In constrast to bitcoin/bitcoin#16497, we need to keep the default non-bech32 for addresses until Segwit is activated on mainnet.
Since Segwit is active in Xaya, we can fully reproduce the Bitcoin change bitcoin/bitcoin#16497. The change made in upstream Namecoin to keep the default at legacy is not needed here.
…2, fixup) fa5a4cd gui: Generate bech32 addresses by default (take 2, fixup) (MarcoFalke) Pull request description: This commit was missing from my previous pull request for some reason 🤔 : * gui: Generate bech32 addresses by default bitcoin#15711 ACKs for top commit: jonasschnelli: Tested ACK fa5a4cd promag: ACK fa5a4cd. fanquake: ACK fa5a4cd Tree-SHA512: 4a38df929d7704bf08e50a2e814b2e6cd25c4165d040a84287045b44e32f4708750845520d64170ea58e41de3ca496da4625d3eb375f9528b21b364c22068a6b
…2, fixup) fa5a4cd gui: Generate bech32 addresses by default (take 2, fixup) (MarcoFalke) Pull request description: This commit was missing from my previous pull request for some reason 🤔 : * gui: Generate bech32 addresses by default bitcoin#15711 ACKs for top commit: jonasschnelli: Tested ACK fa5a4cd promag: ACK fa5a4cd. fanquake: ACK fa5a4cd Tree-SHA512: 4a38df929d7704bf08e50a2e814b2e6cd25c4165d040a84287045b44e32f4708750845520d64170ea58e41de3ca496da4625d3eb375f9528b21b364c22068a6b
This commit was missing from my previous pull request for some reason 🤔 :