Josselin Feist

Hi @paulrberg . We actually worked on the support this week (https://github.com/crytic/slither/pull/1378, https://github.com/crytic/slither/pull/1563). We encountered a couple of edge cases that slowed us down, but we are aiming for a...

This is on hold. Nsc for solidity is outdated and need a refresher

We should also list our streaming

Todo: - Add 2 recording on properties - Add Ethcc slides - Maybe external section? - Add https://github.com/crytic/building-secure-contracts/blob/master/SUMMARY.md

Thanks @hayesgm for the link. So that would work with manual editing, but it will prevent a more transparent usage. Ex: as a user I want to run `some_tool [saddle...

Hi. Is there any update on this PR? It's a neat addition

What are your opinions if we add a `nonPayable` attribute, that would be required a compilation to narrow a function shadowed from payable to non-payable? Because I can see the...

Hi, As @Nanolucas mentioned, it would be awesome if Truffle could emit a warning if the json artifacts are corrupted because of a contract's name reused. We had many issues...

Would it be possible for truffle to emit a warning if one of the top-level element does not generate a json artifact? As we are seeing more and more codebase...

If one of the assertion never passed, we should note it as "not covered " In the more longer term, we should have fined grained information, and show covered/not covered...