zerosnacks

Hi @abhijeetbhagat thanks for your PR, In my opinion, as a principle Foundry does not directly integrate third party services to remain a neutral actor. I am against recording metrics...

Hi @conor10, thanks for your reply >To provide the necessary ENS contract configuration for the various networks we support. Otherwise this will need to be provided by the user, or...

After an internal check with @gakonst and a discussion amongst other core contributors we've decided to not move ahead with this proposal to integrate. Foundry does not distribute or provide...

Hi @conor10 / @abhijeetbhagat, >What matters to us is seeing smart contracts being named with ENS names, so end-users stop seeing hex contract addresses which is just plain wrong. >Then...

Marking as duplicate, there are other tickets that already capture this goal, see: https://github.com/foundry-rs/foundry/issues/7720

Hi all, thank for all the amazing suggestions and feedback! Concretely to improve the verification experience we propose the following: - Provide clear feedback to the user upon failure with...

>What is lacking from Foundry scripts? What are the issues you are running into? Feedback from Uniswap: Mainly multi-chain deployments and verification on multiple explorers at once. We frequently deploy...

> also this goes for @forge-std package Good point, cross-linking https://github.com/foundry-rs/forge-std/issues/170 @o-az and I will be looking into this for the next Foundry release >we will not be silenced I...

Considering the binaries are indeed quite large, totalling > 250mb zipped for all it is indeed a question whether it makes sense to bundle all versions into one package rather...

From a conversation with @pcaversaccio, we must make sure to generate a provenance statement in our release flow; this is similar to our attestation artifacts for our regular binaries. I...