tuturu-tech
tuturu-tech
When generating coverage with Echidna the resulting coverage file reports function and contract names as found/hit: ```solidity 15 | found | contract BitLock is ChallengeBase { 16 | found* |...
Currently `string` types are just byte arrays which don't seem to adhere to any specific encoding, this makes it difficult to correctly decode strings from corpus call sequences in tools...
**Version**: 0.1.3, but also present in 0.1.2 The ABI encoded data field does not match the ABI decoded values in the `inputValues` field of the corpus call sequences. **Uint256:** ```...
Medusa seems to save an empty string in the corpus for a "0x00" string input, which makes correctly parsing the corpus input values more difficult. Example property: ```solidity function check_specific_string(string...
Added very simple json report generation (only lines found/covered) Issues: - Error var is overridden, looking for guidance on how best to handle this - html path is modified in...
### Describe the issue: When multiple contracts have functions with the same signature fuzz-utils will generate the same function multiple times, preventing compilation. We should: - Add a prefix to...
### Describe the desired feature In case of upgradeable contracts we might want to deploy the contracts as proxies and initialize them. This should be automatically handled if we can...
### Describe the desired feature For example: - Include only call sequences whose names are contained in a user provided list - Include only call sequences that contain a call...
### Describe the desired feature The `template` command assumes the project uses Foundry, we should add hardhat support.
### Describe the desired feature - [x] Fix failing Medusa tests by: - [x] Adding a medusa corpus for value transfer - [x] Removing non-failing call sequences from the corpora...