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

Add bytecode hash in README #170

Open
PaulRBerg opened this issue Jul 14, 2023 · 1 comment
Open

Add bytecode hash in README #170

PaulRBerg opened this issue Jul 14, 2023 · 1 comment
Labels
effort: low Easy or tiny task that takes less than a day. good first issue Good for newcomers. 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
Owner

Feedback shared by @SolcAndMe via Telegram:

Would it be possible to link the bytecode hash of the proxy contract in the readme as well? since we need that for the address generation.

@PaulRBerg
Copy link
Owner Author

Example of proxy deployed on Mainnet: 0xBbB288d2ed304C0BdEa4685F7d019e9240a9e9A2.

@PaulRBerg PaulRBerg added good first issue Good for newcomers. priority: 2 We will do our best to deal with this. effort: low Easy or tiny task that takes less than a day. type: docs Changes to documentation. work: obvious work: clear Sense-categorize-respond. The relationship between cause and effect is clear. and removed documentation labels Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: low Easy or tiny task that takes less than a day. good first issue Good for newcomers. 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
Development

No branches or pull requests

1 participant