Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Getting the json results #3

Open
kenneth-lee-ch opened this issue Jul 5, 2022 · 6 comments
Open

Getting the json results #3

kenneth-lee-ch opened this issue Jul 5, 2022 · 6 comments

Comments

@kenneth-lee-ch
Copy link

Would you mind providing the code on how to reproduce the JSON files in the results for the Mythril?

@sujeetc
Copy link
Owner

sujeetc commented Jul 6, 2022

myth a ${main_contract_file} -o json --execution-timeout 86400

@kenneth-lee-ch
Copy link
Author

kenneth-lee-ch commented Jul 6, 2022

But how do you dump the result into a json file? Doesn't that only print the output on the terminal in json format? Also, this doesn't seem effective when you have to process >9k contracts.

@sujeetc
Copy link
Owner

sujeetc commented Jul 7, 2022

myth a ${main_contract_file} -o json --execution-timeout 86400 |& tee -a json_file_name.json

@chinhonglee
Copy link

and did you do that 9k times to get the results for 9k contracts? Would you mind to provide an example on how to do that?

@sujeetc
Copy link
Owner

sujeetc commented Jul 8, 2022

We did automation to do this job.

@chinhonglee
Copy link

A follow-up question, how come there are multiple tx_sequence for a single contract with the same vulnerability type? For example, the Integer Arithmetic Bugs in results/mythril/0x00a0cbe98e4d110b0fa82646152d77babf2951d0_ext_mythril.json? Is it because the contracts have been scanned multiple times to produce duplicate results?

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

No branches or pull requests

3 participants