Namespace conflict with MythX
See original GitHub issuetruffle run verify [MyContract] is the same plugin command used by the MythX plugin. I had to remove truffle-security from plugins to use this one.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
solidity library namespace conflicts · Issue #7644 - GitHub
I would like to use solidity as a library for aleth, but there are namespace conflicts, who can help me solve this problem?...
Read more >MythX: Smart contract security service for Ethereum
Detect security vulnerabilities in your Ethereum smart contracts throughout the development life cycle. Analyze Solidity dapps for security holes and known ...
Read more >Error 40020 (http: 409): Namespace conflict ... - Dell
Cause. The issue is a User Admin can't own more than one namespace. The problem is for ECS 2.2. 0, if the User...
Read more >#6827 (Fix DeleteFile namespace conflict on win32) – MythTV
Win32 builds broke at r21156 due to a namespace conflict with Windows' DeleteFile? macro. The attached patch undefines the problem macro.
Read more >80. Namespaces - 네이버 블로그
The names in any one namespace don't conflict with names in another namespace. The rules governing declaration and definitions in a ...
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

A workaround that could be possible is that both the MythX guys and I define a second command in our truffle-plugin files. Then when both truffle-plugin-verify and truffle-security are installed together, a user could still use both of them by their “fallback” command. For me that would be
truffle run etherscanand perhaps for truffle-security it could betruffle run mythx.This would require no changes at Truffle’s side, and could be a valid workaround while a true solution can be developed on the Truffle side. @gnidan would this work with the current Truffle plugin system?
@danielrea Awesome work!
So as a reference to anyone finding this down the line.
If you want to use both truffle-plugin-verify, and truffle-security in the same project:
0.3.5or higher & truffle-security version1.6.2or higher.truffle run etherscanfor truffle-plugin-verify &truffle run mythxfor truffle-security.