Is there an existing issue for this?

• I have searched the existing issues

SUMMARY

Add support for searching by Consensus Entity ID or Node ID

DESCRIPTION

Node operators need to manage their Entity IDs and Node IDs and it would be easier if they could also use the Explorer for checking what is going on. Registration of non-client nodes and runtimes requires an Entity ID. Every registered node also has a Node ID that it uses for performing transactions.

The search could be implemented either as directly searching for Entity ID (aka entity public key) or Node ID (aka node public key) or as searching for the corresponding Consensus address. The Consensus address from any public key can be derived with:

• oasis-node stake pubkey2address --public_key <public_key> (https://docs.oasis.io/core/oasis-node/cli#pubkey2address)
• https://github.com/oasisprotocol/oasis-core/blob/master/go/common/crypto/address/address.go#L93

Although it is a unclear what the search results should display. For example searching for the Kiln Entity ID "c+Kr/VTZLJes6N2u6nTEj7aWje8wHApJeVEoOdvhCh8=" could return:

• search results for entity account page: https://explorer.oasis.io/search?q=oasis1qqtmpsavs44vz8868p008uwjulfq03pcjswslutz
• validator page (if it is a validator): https://explorer.oasis.io/mainnet/consensus/validators/oasis1qqtmpsavs44vz8868p008uwjulfq03pcjswslutz
• entity page: maybe?

Similarly, searching for Kiln current validator Node ID jKA6PqWwftnglxywnQQPoIcb7j2HQVu7anf2i7LWU2c= could return:

• search results for node account page: https://explorer.oasis.io/mainnet/consensus/address/oasis1qq5c20yqk5cfey43m49h8slqrmm42zd9qg352f53
• validator page (if it figures out this is one of the validator nodes of this entity): https://explorer.oasis.io/mainnet/consensus/validators/oasis1qqtmpsavs44vz8868p008uwjulfq03pcjswslutz
• node page: maybe?

As far as I know with ROFL runtimes this will get even more confusing and we need a consistent way of searching and displaying public keys.