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
Update identifiers specified in CIP5 with prefixed bech32 encoding #295
Comments
|
@rhyslbw: Yes, the API already has support for the Bech32 prefixes specified in CIP5 (including the ones you've listed). |
We recently audited the |
Thanks @intricate and @dcoutts. Please transfer this issue back to |
|
|
Oh, this is not just about addresses! Ok, yes, they might need to be stored both as hex and as Bech32. As for the others, I have found |
Yes, these are the prefixes and their allocations as per the CIP
|
I am not currently aware of any queries that use the raw ByteString version of these fields, so I could just switch then to using the Bech32 encoding rather than duplicating them. Does that make sense? |
Ok,
|
In this case we store both the raw hex and Bech32 encoded version. Closes: #295
Other tools and services are in the process of implementing CIP5, despite it's draft status, so to ensure we're presenting a consistent value, it would be good timing to implement here:
Applicable Prefixes
pool
pool_vk
vrf_vk
The text was updated successfully, but these errors were encountered: