crytic / crytic/crytic-compile

[Bug]: range of compiler versions not supported

Open
#471 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
197
Forks
97
PR merge metrics
No merged PRs in 30d

Description

### Describe the issue:

Slither cannot scan addresses with source code with compile versions range

### Code example to reproduce the issue:

https://optimistic.etherscan.io/token/0x94b008aa00579c1307b0ef2c499ad98a8ce58e58#code

![image](https://github.com/crytic/slither/assets/98317179/14a0ea8b-1e98-4d7a-bee5-0c461239029e)

![image](https://github.com/crytic/slither/assets/98317179/2eaeaaea-d365-46bc-9cdf-3dedb98eba13)

### Version:

0.9.6

### Relevant log output:

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the Etherscan contract linked in the issue and reproduce the failure using version 0.9.6. Trace how compiler-version ranges are handled during the Slither scan. Done means the linked address and its source with a compiler-version range can be scanned successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.