Patricio Palladino

This can be helpful: https://github.com/nodejs/node/blob/d2a13695bf1661f942c51f257a9c8d778b77ff2d/lib/internal/assert/assertion_error.js#L27-L45

This comes from a conversation with Ryan about https://github.com/NomicFoundation/hardhat/pull/3060 — I think `hardhat_setChainId` would be a better alternative to NomicFoundation/hardhat#3060

To give more context: these is one of the builtin tracers that geth has, so we can implement it without having to pull a js engine.

Also faild to reproduce it. Can you provide more details about your environment? I also noticed that yarn install produces tons of errors related to peer dependencies. Personally I'd switch...

I understand this may be a complex feature to implement, but so far it's the only thing that hasn't been amazingly good about Expressive Code. Adding it would be perfect.

I think the title of the issue makes an implicit assumption that we'd just reject working with networks that we don't fully understand/support. This is contrary to how Hardhat Network...

Also, given that these packages aren't used in v3, we should also tag their releases as `latest`, not just `hh2`: - [ ] `@nomicfoundation/hardhat-foundry` - [ ] `@nomicfoundation/hardhat-ledger` - [...

`@nomicfoundation/[email protected]` now works out of the box with all the chains officially supported by Etherscan, Blockscout, and Sourcify.

PSA: `@nomicfoundation/[email protected]` now works out of the box with all the chains officially supported by Etherscan, Blockscout, and Sourcify.

I may have some time in the next week or so to send a PR fixing this. Can I somehow help? Or are you working on it, @Harpush? To me...