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

Provide guidance on how to reproduce bytecodes #741

Open
PaulRBerg opened this issue Dec 9, 2023 · 2 comments
Open

Provide guidance on how to reproduce bytecodes #741

PaulRBerg opened this issue Dec 9, 2023 · 2 comments
Labels
effort: low Easy or tiny task that takes less than a day. priority: 2 We will do our best to deal with this. type: docs Changes to documentation. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.

Comments

@PaulRBerg
Copy link
Member

Third-parties may be interested in reproducing the bytecodes deployed on Mainnet. To assist them, we should provide a wiki or some sort of docs for how to recompile the contracts and passing the appropriate constructor arguments.

More context here:

https://discord.com/channels/883432404780466176/1077650654396428348/1183046520975675462
@PaulRBerg PaulRBerg added type: docs Changes to documentation. priority: 2 We will do our best to deal with this. effort: low Easy or tiny task that takes less than a day. work: clear Sense-categorize-respond. The relationship between cause and effect is clear. and removed documentation labels Jan 1, 2024
@github-actions GitHub Actions

This comment was marked as resolved.

Sign in to view
@github-actions github-actions bot added the stale Inactive for a long time. label Jul 7, 2024
@PaulRBerg

This comment was marked as resolved.

Sign in to view
@PaulRBerg PaulRBerg removed the stale Inactive for a long time. label Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: low Easy or tiny task that takes less than a day. priority: 2 We will do our best to deal with this. type: docs Changes to documentation. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PaulRBerg