We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using the bech32 binary from cardano-wallet v2021-06-11
cardano-wallet v2021-06-11
Piping any address in either upper or lower case fails, including the test inputs on the readme page.
Attempted commands (with or without the underscore, doesn't change outcome):
> echo 706174617465 | ./bech32 base16_ >>>bech32: user error (Unable to detect input encoding. Neither Base16, Bech32 nor Base58.)
> "addr1q9.....kqwymqug" | ./bech32 addr >>>bech32: user error (Unable to detect input encoding. Neither Base16, Bech32 nor Base58.)
I've also tried multiple examples provided around the forums for generating staking addresses from a wallet address with the same results.
The text was updated successfully, but these errors were encountered:
Thanks for reporting @ImminentFate - I can reproduce this on Linux with:
$ printf "706174617465\n" | bech32 base16_ base16_1wpshgct5v5r5mxh0 $ printf "706174617465\r\n" | bech32 base16_ bech32: user error (Unable to detect input encoding. Neither Base16, Bech32 nor Base58.)
As a workaround, you can put your input in a file and save it with UNIX line endings (LF), instead of Windows line endings (CRLF).
Sorry, something went wrong.
No branches or pull requests
Using the bech32 binary from
cardano-wallet v2021-06-11
Piping any address in either upper or lower case fails, including the test inputs on the readme page.
Attempted commands (with or without the underscore, doesn't change outcome):
I've also tried multiple examples provided around the forums for generating staking addresses from a wallet address with the same results.
The text was updated successfully, but these errors were encountered: