-
Notifications
You must be signed in to change notification settings - Fork 200
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
Support for bc1 addresses (Bech32) #12
Labels
bug
Something isn't working
Comments
Hello, |
This would be awesome if you can update this. I use this script a few times a year. Thanks for your efforts on this by the way. |
Hi,
there is an RPC in reference blockchain which, when merged would replace
much of this library functionality. I'm waiting to see what it's fate will
be and then I will decide if to incorporate the bc1 addresses.
Regards
---------- Původní e-mail ----------
Od: linux-mining ***@***.***>
Komu: graymauser/btcposbal2csv ***@***.***>
Datum: 11. 1. 2021 3:02:30
Předmět: Re: [graymauser/btcposbal2csv] Support for bc1 addresses (Bech32) (
#12)
"
This would be awesome if you can update this. I use this script a few times
a year. Thanks for your efforts on this by the way.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
(#12 (comment))
, or unsubscribe
(https://github.com/notifications/unsubscribe-auth/AIMF5VSU6Q7DUW5EQAN4KNDSZJL23ANCNFSM4VOWFH4A)
.
"
|
I have PRed changes to support |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that the converter doesn't support the new BTC address format that starts with bc1 and is usually longer in length.
example:
37XuVSEpWW4trkfmvWzegTHQt7BdktSKUs (older format)
bc1qgdjqv0av3q56jvd82tkdjpy7gdp9ut8tlqmgrpmv24sq90ecnvqqjwvw97 (new format)
This is the error when it tries to convert it:
The text was updated successfully, but these errors were encountered: