https://polkadot.subsquare.io/referenda/1741
Sorry but your assessment is not accurate, please review the documentation in more detail:
There is no Validator Addressing information in any Polkadot "feature". Node addressing needs a low level crawl of the P2P network, accessing the Distributed Hash Table in order to verify where authorities (Validators) live in the network.
This is something implemented by our toporacle rust component. Then crossed with premium geolocation data and offered to the ecosystem in form a APIs.
Subscan could never provide this feature, becasue subscan indexes the blockchain data and this information is not in the blockchain at all.
Ecosystem services, such as the staking dashboard can display polkawatch information using our API:
Sorry but your assessment is not accurate, please review the documentation in more detail:
There is no Validator Addressing information in any Polkadot "feature". Node addressing needs a low level crawl of the P2P network, accessing the Distributed Hash Table in order to verify where authorities (Validators) live in the network.
This is something implemented by our toporacle rust component. Then crossed with premium geolocation data and offered to the ecosystem in form a APIs.
Subscan could never provide this feature, becasue subscan indexes the blockchain data and this information is not in the blockchain at all.
Ecosystem services, such as the staking dashboard can display polkawatch information using our API:
