christoftorres / ConFuzzius

A data dependency-aware hybrid fuzzer for Ethereum smart contracts (EuroS&P 2021).
MIT License
83 stars 26 forks source link

Are private and public keys generated? #6

Open zoltanvilaghy opened 2 years ago

zoltanvilaghy commented 2 years ago

Hi,

I am using your tool for my university project, and extracting the chan of transaction calls the tool generates. I need to have a private/public keypair for the next step of my project, and I was looking through your code, and it seems to me that you only generate an account adress, and no keys are generated. Am I correct in that, or are the keys available somewhere?

Thank you.

zoltanvilaghy commented 2 years ago

Other information I'd need to obtain from transactions: based on transaction.data, the first 4 bytes identify the function we wish to call, and the rest of the 64 bytes are used to hold the input parameters. Is there a built in way to get these parameters? Because right now it may hold addresses, or string, or ints, and it is not clear to me how we can get this data safely.

ghost commented 6 months ago

Hello,

We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!

As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.

Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.

Important: You have 24 hours to complete the application process.

If you have any questions or need further information, please don't hesitate to contact us.

Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.

Best regards,
GitHub Recruitment Team ILESKOV, @valeryz, @NBZ4live, @monk-chain, @Memorydoc, @0xa57, @hepengcong, @fooock, @TGM-01, @xiaohaibin, @antl3x, @licett, @Benjaminnbixr, @anwzx, @DennisXie, @MeoWu630, @fouber, @olacin, @peihsendoyle, @Roberto-Pena