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

[SPEC ONLY?]: Validator Ethereum + L2s heartbeart and performance metric #1993

Open
gordsport opened this issue Oct 16, 2023 · 1 comment · May be fixed by #2027
Open

[SPEC ONLY?]: Validator Ethereum + L2s heartbeart and performance metric #1993

gordsport opened this issue Oct 16, 2023 · 1 comment · May be fixed by #2027
Assignees
Labels
🐕 validators validators - feature development work stretch
Milestone

Comments

@gordsport
Copy link
Contributor

gordsport commented Oct 16, 2023

@gordsport gordsport added this to the 🏰 Palazzo Mistero milestone Oct 16, 2023
@gordsport gordsport added the 🐕 validators validators - feature development work label Oct 16, 2023
gordsport added a commit that referenced this issue Nov 1, 2023
Copied from #2026 with the base as the `palazzo` branch.

close #1993 .
@gordsport gordsport linked a pull request Nov 1, 2023 that will close this issue
@gordsport gordsport linked a pull request Nov 1, 2023 that will close this issue
@gordsport
Copy link
Contributor Author

If we are planning to do this after the Palazzo release we should take into account the other Ethereum RPC chains as detailed in:

@gordsport gordsport changed the title Validator Ethereum heartbeart and performance metric Validator Ethereum + L2s heartbeart and performance metric Jan 29, 2024
@gordsport gordsport added stretch and removed parked labels Jan 29, 2024
@gordsport gordsport changed the title Validator Ethereum + L2s heartbeart and performance metric [SPEC ONLY?]: Validator Ethereum + L2s heartbeart and performance metric Jan 29, 2024
gordsport added a commit that referenced this issue Feb 22, 2024
Copied from #2026 with the base as the `palazzo` branch.

close #1993 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment