Ability to specify entry point contract by name
See original GitHub issueThe title is pretty self-explanatory. 😄
The motivation for asking this is:
Mythril doesn’t currently handle the dependencies from Dapphub’s dapp
tool and when using a merger tool to solve dependencies (like solidity-merger
) the contract being analyzed is always the last one (per solc
requirements).
If we could specify the entry point the merging tools would be a working solution!
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
entry_points | SmartPy Documentation
An entry point is a method of a contract class that can be called from the outside. Entry points need to be marked...
Read more >Enter Into a Contract: Everything You Need to Know
When you enter into a contract, it is important to follow several rules to ensure the contract is valid and enforceable in a...
Read more >How to Sign and Execute Binding Contracts | LawDepot
Ensure your next contract is binding by learning about the elements of a valid contract, best signing practices, witness requirements, ...
Read more >Part 6 - Competition Requirements | Acquisition.GOV
This part prescribes policies and procedures to promote full and open competition in the acquisition process and to provide for full and ...
Read more >Michelson: the language of Smart Contracts in Tezos
The specified entrypoint did not exist. ... name is a pattern that matches any stack and names it in order to use it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I added the following behavior for solc files that contain multiple contracts.
This will analyze the last bytecode entry generated by solc:
This will analyze the contract
OMGToken
in the fileOmiseGo.sol
:That would be an option, but I am thinking it might be better to remove Mythril’s source code input options altogether and leave the compiling and linking to the build environment. Otherwise, a lot of complicated logic has to be implemented and it will be difficult to cover the various types of imports etc… This is high up on my list, just need to play more with Truffle and Dapp.