You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is related to the paper "Cross-Modality Mutual Learning for Enhancing Smart Contract Vulnerability Detection on Bytecode".
1. In Table 4 of APPENDIX B of the paper, IO.contract is 1,368/7,183. However, when looking at the data of resource 2 of this repository, there are only 275 Integeroverflows. Why is there a difference? Which data is uploaded?
2. The ground truth label in resource 2 says that manual verification is performed after the instruction. How did you perform the manual verification? Did you check that SafeMath and require were included without exception? Are there any other criteria that you considered?
This time, it is related to "Rethinking Smart Contract Fuzzing: Fuzzing With Invocation Ordering and Important Branch Revisiting".
3. In the ground_turth_label.csv of resource 3, the 9.sol file (contract name: WWW) of the Integer Overflow/Underflow sheet is set as ground truth 1. Is there a reason why it is set to 1?
Both function "transfer" and "transferFrom" have "require", which is a guard for the minus operation, and in the case of the plus operation, it is limited to a constant in the constructor, so it seems that overflow does not occur, so I am asking a question.
The text was updated successfully, but these errors were encountered:
I have a question.
It is related to the paper "Cross-Modality Mutual Learning for Enhancing Smart Contract Vulnerability Detection on Bytecode".
1. In Table 4 of APPENDIX B of the paper, IO.contract is 1,368/7,183. However, when looking at the data of resource 2 of this repository, there are only 275 Integeroverflows. Why is there a difference? Which data is uploaded?
2. The ground truth label in resource 2 says that manual verification is performed after the instruction. How did you perform the manual verification? Did you check that SafeMath and require were included without exception? Are there any other criteria that you considered?
This time, it is related to "Rethinking Smart Contract Fuzzing: Fuzzing With Invocation Ordering and Important Branch Revisiting".
3. In the ground_turth_label.csv of resource 3, the 9.sol file (contract name: WWW) of the Integer Overflow/Underflow sheet is set as ground truth 1. Is there a reason why it is set to 1?
Both function "transfer" and "transferFrom" have "require", which is a guard for the minus operation, and in the case of the plus operation, it is limited to a constant in the constructor, so it seems that overflow does not occur, so I am asking a question.
The text was updated successfully, but these errors were encountered: