Bech32 on IRISnet

Bech32 is a new Bitcoin address format proposed by Pieter Wuille and Greg Maxwell. Besides Bitcoin addresses, Bech32 can encode any short binary data. In the IRIS network, keys and addresses may refer to a number of different roles in the network like accounts, validators etc. The IRIS network is designed to use the Bech32 address format to provide robust integrity checks on data. The human readable part(HRP) makes it more efficient to read and the users could see error messages. More details in bip-0173

Human Readable Part Table

HRP Definition
iaa IRISnet Account Address
iap IRISnet Account Public Key
iva IRISnet Validator's Operator Address
ivp IRISnet Validator's Operator Public Key
ica Tendermint Consensus Address
icp Tendermint Consensus Public Key


Not all interfaces to users IRISnet should be exposed as bech32 interfaces. Many addresses are still in hex or base64 encoded form.

To covert between other binary representation of addresses and keys, it is important to first apply the Amino encoding process before bech32 encoding.

Account Key Example

Once you create a new address, you should see the following:

NAME:    TYPE:           ADDRESS:                                PUBKEY:
test1    local    iaa18ekc4dswwrh2a6lfyev4tr25h5y76jkpclyxkz    iap1addwnpepqgxa40ww28uy9q46gg48g6ulqdzwupyjcwfumgfjpvz7krmg5mrnwk5xq9l

This means you have created a new address iaa18ekc4dswwrh2a6lfyev4tr25h5y76jkpclyxkz, its hrp is iaa. And its public key could be encoded into iap1addwnpepqgxa40ww28uy9q46gg48g6ulqdzwupyjcwfumgfjpvz7krmg5mrnwk5xq9l, its hrp is iap.

Validator Key Example

A Tendermint Consensus Public key is generated when the node is created with iris init. You can get this value with

iris tendermint show-validator --home=<iris_home>

Example output: