Matt Solomon

That's true, I am equally supportive of a library, which does have the nice side effect of free namespacing of the constants. My nit there would be to name it...

> perhaps could make sense to somehow sync https://github.com/foundry-rs/forge-std/blob/master/src/StdChains.sol#L180 automatically with viem? It's a bit sad that support of chains is so different between: The best I can think of...

Makes sense, so you can get the chain ID from a human readable name using the `getChain(string)` method, for example `getChain("mainnet").chainId`. Here's a forge-std that does this: https://github.com/foundry-rs/forge-std/blob/1d9650e951204a0ddce9ff89c32f1997984cef4d/test/StdCheats.t.sol#L404

Right, it's just a string so it won't autocomplete. Probably could add an enum that has all the same strings as the enum values, along with a `getChain(enum ChainAliases)` overload

Ohh I like this idea. Addresses would vary by chain, so it seems like this might be a good way to extend the [`Chain`](https://github.com/foundry-rs/forge-std/blob/a2edd39db95df7e9dd3f9ef9edc8c55fefddb6df/src/StdChains.sol#L49-L61) return type. Perhaps we create a...

Closing as stale for now

For large ranges I agree logarithmic distribution is preferable > > Note: contrarily to `bound`, `boundLog` WILL NOT return `x` when the input `x` is within the provided [`2**min`, `2**(max+1)-1`]...

cc @grandizzy @klkvr for thoughts

Yea the UX for this was always the trickiest, in the past we also considered just using the inline config which could be a good approach: ```solidity /// forge-config: default.fuzz.range.x...

> Yep, agree, maybe we should start an issue in foundry to track / implement these? That sounds good to me, would you mind creating that? :)