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

2024 Dec 16 - Protocol Team Checkin #12

Closed
tynes opened this issue Dec 11, 2024 · 2 comments
Closed

2024 Dec 16 - Protocol Team Checkin #12

tynes opened this issue Dec 11, 2024 · 2 comments
Labels
U-node Upgrade: involving changes to node component (cl, el, etc.)

Comments

@tynes
Copy link

tynes commented Dec 11, 2024

Please comment on this issue for things you would like to discuss during the protocol team checkin meeting

@emhane
Copy link
Member

emhane commented Dec 11, 2024

more labels. definitely labels "contract" and "client" to make distinction if it's a client upgrade or contract upgrade. for client upgrade issues, more labels about what part of the code is effected would be helpful, similar the labels available in reth for example.

@protolambda
Copy link
Contributor

For the agenda:

@protolambda protolambda added the U-node Upgrade: involving changes to node component (cl, el, etc.) label Dec 16, 2024
@protolambda protolambda changed the title 2024-16-09 Protocol Team Checkin 2024 Dec 16 - Protocol Team Checkin Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
U-node Upgrade: involving changes to node component (cl, el, etc.)
Projects
None yet
Development

No branches or pull requests

3 participants