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

Support partial matches in contract verifier #3190

Open
perekopskiy opened this issue Oct 29, 2024 · 0 comments
Open

Support partial matches in contract verifier #3190

perekopskiy opened this issue Oct 29, 2024 · 0 comments

Comments

@perekopskiy
Copy link
Contributor

🌟 Feature Request

📝 Description

Please first read about full vs partial matches for contract verification here. Currently contract verifier support only full matches. This request is for supporting partial matches. Verification logic should be updated so that if a full match wasn't found but there is a partial one then the request is persisted and API exposes its data. Also, if a contract is partially verified it should be possible to replace its verification info if some full match request comes in, but not vice versa.

🤔 Rationale

Partial match is useful when the original source code was lost after deployment but developer managed to replicate it apart from metadata. Also, etherscan performs only partial match so devs get used to it. There are cases when only partial match verification is possible without adding a new feature to contract verifier, e.g. when contract's libraries are linked dynamically.

📋 Additional Context

After it's done on backend side it would be nice to display verification type on frontend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant