⛓
ChainID and Address
Bronos has different Chain ID to distinguish between devnet, testnet and mainnet. When running the Bronos in your local environment, you will also need to decide your own Chain ID.
For example, our devnet Chain ID is
bronostestnet_9000-1.BIP-0173 defines a new format for segregated witness output addresses that contains a human-readable part that identifies the coin type. Bronos uses different address prefix compared to other chains, Its address prefix is
brc.
Bronos uses the Bech32 address format wherever users must handle binary data. Bech32 encoding provides robust integrity checks on data and the human readable part(HRP) that provides contextual hints that can assist UI developers with providing informative error messages. Specifically, we have the following HRP prefix for different addresses types in the mainnet:
Text | Address bech32 prefix |
|---|---|
Account | brc |
Validator | brcvaloper |
Consensus Nodes | brcvalcons |
We can use the
keys show command for bronosd with the flag --bech <type> (acc|val|cons) to obtain the addresses and keys as mentioned above: for example,
$ bronosd keys show mykey --bech acc
- name: mykey
type: local
address: brc1ag9j0qv6jxxel5t5fggjw86m8nxw638aafwe9c
pubkey: '{"@type":"/ethermint.crypto.v1.ethsecp256k1.PubKey","key":"Ai4YWUBoJY8Kyyyw5wSC+XVVf2nf3xp6XsO5ECd4vqEa"}'
mnemonic: ""
$ bronosd keys show mykey --bech val
- name: mykey
type: local
address: brcvaloper1ag9j0qv6jxxel5t5fggjw86m8nxw638a02nt8p
pubkey: '{"@type":"/ethermint.crypto.v1.ethsecp256k1.PubKey","key":"Ai4YWUBoJY8Kyyyw5wSC+XVVf2nf3xp6XsO5ECd4vqEa"}'
mnemonic: ""
$ bronosd keys show mykey --bech cons
- name: mykey
type: local
address: brcvalcons1ag9j0qv6jxxel5t5fggjw86m8nxw638ameqhtq
pubkey: '{"@type":"/ethermint.crypto.v1.ethsecp256k1.PubKey","key":"Ai4YWUBoJY8Kyyyw5wSC+XVVf2nf3xp6XsO5ECd4vqEa"}'
mnemonic: ""
Last modified 8mo ago