search

pcaversaccio / createx

Factory smart contract to make easier and safer usage of the `CREATE` and `CREATE2` EVM opcodes as well as of `CREATE3`-based (i.e. without an initcode factor) contract creations.
https://createx.rocks
GNU Affero General Public License v3.0
342 stars 26 forks source link

💥 Turn the `customChains` Object Into a Separate Package #58

Closed PaulRBerg closed 7 months ago

PaulRBerg commented 11 months ago

Describe the desired feature:

It would be nice if this JSON object were available as an npm package:

https://github.com/pcaversaccio/createx/blob/8bb34bee6251899f11b8bf9cbb8c98bd30efdf5f/hardhat.config.ts#L555

pcaversaccio commented 11 months ago

@fvictorio is this something that you would like to maintain from Hardhat's side?

mds1 commented 11 months ago

I wonder if this is better maintained in viem, as their chains already maintains RPC URLs, block explorers, and the Multicall3 contract (example), cc @jxom @tmm

pcaversaccio commented 11 months ago

Whatever works best for the ecosystem; also pinging @alcuadrado from HH. Let's just coordinate in a way that the implementation is interoperable and independent of the framework used.

fvictorio commented 10 months ago

+1 to having a common package for common chains information. This could be used from viem to build their chains object, from hardhat-verify for the explorers configuration, from Hardhat configs, and surely for a lot of other use cases.

pcaversaccio commented 10 months ago

@jxom @tmm any views on the above?

pcaversaccio commented 7 months ago

Closing this issue since I personally won't tackle it and Hardhat / Viem are obviously now aware of it and can track it in their own roadmaps.