-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add search by validator key to whois #339
Conversation
whois/src/main.rs
Outdated
let node_network_id = node.details.network_id.clone(); | ||
if node_network_id == Some(network_id) { | ||
*holder = Some(node.node_id); | ||
fn save_node_id(node: &AddedNode, authority_key: AccountId32, holder: &mut Option<FeedNodeId>) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cannot we just return an Option<FeedNodeId>
, as the current approach reminds me the plain C one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I have 2 questions:
- how does this relate to Telemetry support #283
- does it still require interaction to select chain before it outputs information ?
Yeah, the telemetry collects data from different chains. Polkadot telemetry, for example, has data from polkadot and kusama with their parachains. So we need to specify our chain. Another option could be to go throw all the chains, subscribing and receiving a few first messages, then resubscribing to another chain. But I can't sat I like it. |
It should partially close the requirements of validator key tracking |
No description provided.