Mike Shultz

> We could add those configs separately to the `ape-solidity` config so the user could sometimes do this: I don't think this makes much sense (for our problem). This basically...

Also, thinking about this and testing a bit more, we probably shouldn't allow absolute paths here (nor resolve anything to absolute paths) because they are likely to be different across...

- Core side PR: https://github.com/ApeWorX/ape/pull/1897 - ape-solidity PR: https://github.com/ApeWorX/ape-solidity/pull/133 Need to get the docs correct with the latest revision but the code should be ready for review.

Just adding some context I ran into for anyone that needs to reference in this issue. Was just looking around and it looks like Vyper also [had some CBOR metadata...

This feature will be availible in the next release of the [`ape-solidity` plugin](https://github.com/ApeWorX/ape-solidity). For some information on how to use it, [see the compiler documentation](https://docs.apeworx.io/ape/stable/userguides/compile.html#settings).

Pending some package releases, traces will now show for the `Web3Provider`, `ape-foundry`'s provider, and `ape-hardhat`'s provider. Let us know if this doesn't cover your needs.

> WIll note that I do not believe that the docker images build until they hit `main`, so just verify it locally and we can merge I did verify that...

Relevant `MockDongle` change: https://github.com/mikeshultz/ledger-eth-lib/commit/611798ff6b4304f12c6390653654fa579818da52#diff-e52e4ddd58b7ef887ab03c04116e676f6280b824ab7469d5d3080e5cba4f2128R45

Took a couple hours of approving signatures on a hardware device, but it seems that signatures start failing at chain ID of `4294887296`. ```python >>> 0b11111111111111111111111111111111 - 4294887296 79999 ```...

My iterator in my test was added on top of a start number, which was `80001`... FFS Okay, so, it seems the limit is a 32-bit number. At least that's...