Skip to content

Issues: crytic/medusa

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.

Sign up for GitHub

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

71 Open 104 Closed
71 Open 104 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Use defaults when partial config is provided instead of requiring all options to be specified explicitly
#361 opened May 28, 2024 by ggrieco-tob
1
Display failed tests
#355 opened May 7, 2024 by aviggiano
1
1
Remove use of global logger in cmd package very-low-priority
#340 opened Mar 27, 2024 by anishnaik
Adjust corpus call sequence encoding of string types so that they are utf-8 compatible
#339 opened Mar 21, 2024 by tuturu-tech
Inconsistency in the corpus encoded and decoded data
#338 opened Mar 21, 2024 by tuturu-tech
Feature: Add ability to deterministically deploy bytecode to specific addresses
#333 opened Mar 15, 2024 by anishnaik
1
CLI warning on go build for malformed/unidentified symbol
#331 opened Mar 13, 2024 by 0xicingdeath
3
Print out events emitted in assertion failure callstack
#330 opened Mar 12, 2024 by 0xicingdeath
Allow pinning to the value of specific storage variables for all failed call sequences
#329 opened Mar 12, 2024 by 0xicingdeath
Differentiate a property that did not execute and a property that ran successfully
#328 opened Mar 12, 2024 by 0xicingdeath
revert in property function is treated as failure and a trace is not given
#327 opened Mar 12, 2024 by 0xalpharush
1
commands to interact with corpus test results
#326 opened Mar 11, 2024 by 0xalpharush
1
coverage report ideas
#325 opened Mar 11, 2024 by 0xalpharush
2
let user know that there is a failing test case in corpus on startup
#321 opened Mar 10, 2024 by 0xalpharush
display solidity source of current PC and bytecode if execution reverts during deployment
#320 opened Mar 9, 2024 by 0xalpharush
1
Add M1 build image support to CI/CD very-low-priority
#317 opened Mar 4, 2024 by Xenomega
1
Add logs format option
#316 opened Mar 4, 2024 by aviggiano
1
Consume arguments emitted from events to be used in the fuzzing test
#311 opened Feb 29, 2024 by 0xicingdeath
1
Medusa can't solve the ByteBattle fuzzing challenge but Echidna can solve it instantly high-priority
#307 opened Feb 22, 2024 by devdacian
Option to set Medusa initial balance using integers same as Echidna
#306 opened Feb 22, 2024 by devdacian
1
Medusa can no longer solve the RarelyFalse fuzzing challenge high-priority
#305 opened Feb 22, 2024 by devdacian
Improve logging API and usage in the cmd package very-low-priority
#300 opened Feb 20, 2024 by anishnaik
3
Remove contract XXX statement in coverage low-priority planning This issue is currently in a planning/discussion phase and should not be implemented yet.
#286 opened Jan 18, 2024 by 0xicingdeath
Calculate and show branch coverage per file planning This issue is currently in a planning/discussion phase and should not be implemented yet. very-low-priority
#285 opened Jan 17, 2024 by 0xicingdeath
Save coverage throughout execution medium-priority planning This issue is currently in a planning/discussion phase and should not be implemented yet.
#280 opened Jan 10, 2024 by 0xicingdeath
ProTip! Updated in the last three days: updated:>2024-05-26.