Skip to content
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

Ping multisig #137

Merged
merged 6 commits into from
Oct 4, 2024
Merged

Ping multisig #137

merged 6 commits into from
Oct 4, 2024

Conversation

pavelkrolevets
Copy link
Contributor

Closes #128

  • update pong to include fields Multisig, EthClientConnected
  • logs indicate if operator has multisig support and connected to eth1 network

Comment on lines +116 to +117
Multisig bool
EthClientConnected bool
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need both? isn't it enough just multisig? it won't be working without eth, right ?

Copy link
Contributor Author

@pavelkrolevets pavelkrolevets Oct 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we check connection to eth client when start operator, if no it cant start, but we can loose it after we started. So we can be Multisig=true and EthClientConnected=false.
For old operator versions we dont have both fields so it will be false, false.
If we have only EthClientConnected then we cant distinguish between old and new version, only comparing version. So Multisig is rather informational for users not to compare versions, as old will be always false

Please let me know if it makes sense.

for _, s := range servers {
ips = append(ips, s.HttpSrv.URL)
}
require.NoError(t, err)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what err are you checking?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@MatusKysel MatusKysel merged commit c1036e1 into unstable Oct 4, 2024
1 check passed
@pavelkrolevets pavelkrolevets deleted the ping-multisig branch October 8, 2024 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add --multisig Flag to Ping Command to Verify Multisig Support
2 participants