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

feat: dynamically upgrade side-loaded contract implementations #223

Closed
seanmcgary opened this issue Feb 6, 2025 · 0 comments · Fixed by #237 · May be fixed by #265
Closed

feat: dynamically upgrade side-loaded contract implementations #223

seanmcgary opened this issue Feb 6, 2025 · 0 comments · Fixed by #237 · May be fixed by #265
Assignees
Labels
enhancement New feature or request

Comments

@seanmcgary
Copy link
Member

seanmcgary commented Feb 6, 2025

For contracts that have been side-loaded for indexing, that are not EigenLayer core contracts, provide the ability to detect contract upgrades and follow a list of prioritized sources to fetch the ABI from:

  1. IPFS - the solc compiler with automatically include the IPFS hash of the ABI file in the contracts bytecode. Out of the box, Forge allows the compiler to publish their ABIs to sourcify which will publish to IPFS [1].
  2. Etherscan - as a fallback option, Etherscan can be used to download the ABI, assuming that it has been uploaded by whoever compiled and deployed the contract. This should be a runtime option since it will require an API key.

[1] https://docs.sourcify.dev/blog/talk-about-onchain-metadata-hash/

@seanmcgary seanmcgary added the enhancement New feature or request label Feb 6, 2025
@seanmcgary seanmcgary changed the title feat: dynamically upgrade core contract implementations feat: dynamically upgrade side-loaded contract implementations Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment