Use bech32 addresses by default #1717
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Drop mention of p2sh-segwit. We should encourage users to use bech32.
sstone
approved these changes
Mar 5, 2021
tompro
pushed a commit
to tompro/eclair
that referenced
this pull request
Mar 7, 2021
Drop mention of p2sh-segwit. We should encourage users to use bech32.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Drop mention of p2sh-segwit. We should encourage users to use bech32.
This doesn't change our internal behavior in practice.
I also bumped the minimal bitcoin core version to 0.18.0 (it was mentioned in our documentation but not enforced at start-up).