sunbeomso

@montyly [1] ``sudo docker exec CONTAINER_NAME manticore //tmp/test.sol --solc solc-0.4.25 --contract BitcoinAgileToken`` With the command above, Manticore successfully begins analysis without error messages. [2] ``$ sudo docker exec CONTAINER_NAME crytic-compile...

@montyly > I can't reproduce the issue locally, could you share how the container was created? I created the container as follows (which seems there is no unusual part for...

@montyly > I can't reproduce the issue locally, Could you try my steps described above? _I have just tried again my steps above without any modifications, and I double-checked that...

@montyly Hi, could you tell me about the progress of this issue? With the latest Manticore (v.0.3.4), I still encounter problems (Manticore produces ``Invalid solc compilation`` messages for contracts that...

Please make sure that you installed the solc binary named ``solc_0.8.7``, as explained in the readme. Also, your input source code should be compiled by that solc. If this answer...

Hi @acmRecife, In order to diagnose the problem concretely, could you provide the source code of your input Solidity contract and the entire command that can reproduce the problem you...

Hi, I can help you if you ask me a specific question. Thank you.

Thanks for your reply. I am still wondering how the manual analysis is conducted. If possible, could you explain in more detail using an example below? https://github.com/SoftSec-KAIST/Smartian/blame/main/examples/bc/SC.bin Or, could you...

When I ran sGuard by providing the name of the main contract, sGuard produced a similar error message: ``` /home/ssb/sGuard/src/index.js:39 const { attributes: { name } } = children.find(({attributes: {...

@duytai Thanks for the answer. Regarding the answer for [Q1], it seems all functions that have the same signatures in different contracts should be renamed when using sGuard. I think...