Skip to content
This repository has been archived by the owner on Jun 3, 2020. It is now read-only.

Consider support different consensus pubkey prefix by config? #178

Closed
chengwenxi opened this issue Feb 22, 2019 · 2 comments
Closed

Consider support different consensus pubkey prefix by config? #178

chengwenxi opened this issue Feb 22, 2019 · 2 comments

Comments

@chengwenxi
Copy link

The consensus key bech32 prefix is a ​​const cosmosvalconspub, it's seems better to add the prefix in config file for different chain.

@chengwenxi chengwenxi changed the title Consider support different consensus pubkey prefix by config Consider support different consensus pubkey prefix by config? Feb 22, 2019
@tarcieri
Copy link
Contributor

tarcieri commented Feb 22, 2019

Absolutely. I guess it's a question of how to interpret the HRP such that it works across different Tendermint networks. Is *pub[base32] sufficient?

@tarcieri
Copy link
Contributor

#181 contains some initial work to generalize the keys

tarcieri pushed a commit that referenced this issue Mar 9, 2019
Adds a `chain::REGISTRY` (as a `lazy_static`) to tmkms, populated from
the configuration file.

Uses this registry when serializing keys to select the appropriate
serialization format.
tarcieri pushed a commit that referenced this issue Mar 10, 2019
Adds a `chain::REGISTRY` (as a `lazy_static`) to tmkms, populated from
the configuration file.

Uses this registry when serializing keys to select the appropriate
serialization format.
tarcieri added a commit that referenced this issue Mar 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants