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.

Sign up for GitHub

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

Jump to bottom

[Feature Request]: Restore bytecode check CI workflow #848

Open
2 tasks done
tamtamchik opened this issue Sep 4, 2024 · 0 comments
Open
2 tasks done

[Feature Request]: Restore bytecode check CI workflow #848

tamtamchik opened this issue Sep 4, 2024 · 0 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@tamtamchik
Copy link
Member

Summary

Need to restore the https://github.com/lidofinance/lido-dao/blob/master/.github/workflows/assert-bytecode.yml pipeline.

Problem

assert-bytecode tries to verify the up-to-date bytecode against the deployed one available through the deployed-* artifacts

Implementation

It should be redone using diffyscan

Guidelines
@tamtamchik tamtamchik added the enhancement New feature or request label Sep 4, 2024
@tamtamchik tamtamchik changed the title [Feature Request]: Add bytecode assertion to master branch CI checks [Feature Request]: Restore bytecode assertion to master branch CI checks Sep 4, 2024
@tamtamchik tamtamchik changed the title [Feature Request]: Restore bytecode assertion to master branch CI checks [Feature Request]: Restore bytecode check CI workflow Sep 4, 2024
@tamtamchik tamtamchik assigned tamtamchik and unassigned tamtamchik Sep 9, 2024
@tamtamchik tamtamchik added the wontfix This will not be worked on label Sep 9, 2024
@tamtamchik tamtamchik transferred this issue from another repository Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tamtamchik