there are some significant issues about vyper that anyone using it would/should be aware of: https://blog.ethereum.org/2020/01/08/update-on-the-vyper-compiler

there are some significant issues about vyper that anyone using it would/should be aware of: https://blog.ethereum.org/2020/01/08/update-on-the-vyper-compiler https://blog.ethereum.org/2020/01/08/update-on-the-vyper-com... that’s not to discredit anyone using vyper, just that when putting “billions of dollars” in play on a project like this, you better have teams of folks looking into the security implications of using such a technology with known caveats that the ethereum foundation team publicised. now things may have changed in the meanwhile between the time that notice was published and now, but if you are using or recommending vyper, it’s worth it to ask or state explicitly “which” vyper and “which version” of vyper, or “did you fork vyper in order to fix some of the issues outlined in the audit” as well as “if you are using vyper in critical applications, are you contributing your fixes back to the community?” If some of the answers are "the ethereum foundation team are too conservative" "the audit doesn't mean anything" "we don't have anyone looking into the security aspects of vyper" then you have your answer: they're going to get hacked.