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
Regtest bech32 address support #110
Conversation
We really need to move to a https://github.com/rust-bitcoin/bitcoin-constants lib so that we dont have to keep doing network-tag-enum conversion. |
@TheBlueMatt happy to get this integrated as is or you consider the refactoring to bitcoin-constants as blocking? |
Not for something as simple as this, no, but it really needs to happen.
…On July 27, 2018 12:26:02 AM UTC, Franck Royer ***@***.***> wrote:
@TheBlueMatt happy to get this integrated as is or you consider the
refactoring to bitcoin-constants as blocking?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#110 (comment)
|
@TheBlueMatt can you advise how I can get this merged? 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.
I'll merge for now. bitcoin-constants
is a hard project to get right - every addition to a public enum requires a major version bump, which then requires all downsteam users to do a major version bump, and it's easy for people to be disrupted by changes to constants that they don't even care about.
Bump version to 0.13
Fix the GetNetworkInfoResult time_offset field
policy: Corrected an inverted documentation for `Older` and `After`
In the spirit of #84, add support for regtest bech32 addresses that start with "bcrt1".
Also added a test that I had added locally when updating rust-bitcoin with my rust-bech32-bitcoin/regtest library.
Please consider this PR, thanks!