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

Prefer latest added bytecode in ContractsIdentifier when the match is not exact #258

Open
fvictorio opened this issue Dec 18, 2023 · 0 comments

Comments

@fvictorio
Copy link
Member

If we lookup a contract using its bytecode and we get an exact match, then it's clear that we should use that contract.

Sometimes, though, we can get several partial matches with the same length. This is especially likely if the matches diverge only in the trailing metadata.

How this will actually be implemented in practice depends on how the codebase is modeled and the relationship of that model with the contracts identifier.

@fvictorio fvictorio added this to EDR Apr 24, 2024
@github-project-automation github-project-automation bot moved this to Unconfirmed in EDR Apr 24, 2024
@fvictorio fvictorio moved this from Unconfirmed to Todo in EDR Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant