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
for the upcoming change in the governance/catalyst voting, a new bech prefix for public/private keys was defined. cardano-foundation/CIPs#342
private/signing key prefix: gov_sk public/verification key prefix: gov_vk
gov_sk
gov_vk
however, these prefixes are not working with the current release of the cardano-serialization-lib in commands like .PublicKey.from_bech32(bechstr)
.PublicKey.from_bech32(bechstr)
please add support for those new prefixes, we need it also for current testing.
or is the prefix limited to only ed25519_pk & ed25519_sk prefixes in general and all other prefixes must be encoded/decoded with a bech32 lib?
ed25519_pk
ed25519_sk
The text was updated successfully, but these errors were encountered:
No branches or pull requests
for the upcoming change in the governance/catalyst voting, a new bech prefix for public/private keys was defined.
cardano-foundation/CIPs#342
private/signing key prefix:
gov_sk
public/verification key prefix:
gov_vk
however, these prefixes are not working with the current release of the cardano-serialization-lib in commands like
.PublicKey.from_bech32(bechstr)
please add support for those new prefixes, we need it also for current testing.
or is the prefix limited to only
ed25519_pk
&ed25519_sk
prefixes in general and all other prefixes must be encoded/decoded with a bech32 lib?The text was updated successfully, but these errors were encountered: