joshieDo
joshieDo
Linked the above PR that taclkes this issue. However, it won't fix anything if the indexer takes 2 mins. But I think waiting 25 seconds for a contract should be...
Seems like the CREATE2 deployer we use `0x4e59b44847b379578588920ca78fbf26c0b4956c` is not deployed on arbitrum.
yeah, i agree for it to be moved to `forge-std` instead
> non-exclusive access to the device (multiple futures trying to use it at the same time?) Leaning towards this. I don't have access to a ledger anymore, but I remember...
Being an `Invalid API Key`, it leads me to believe that you're somehow calling it with wrong API Keys or with wrong chain ids. For example, avalanche/fuji key != ethereum/mainnet/goerli...
Still going to add simple tests, but opening the PR already for review.
added tests
resolved pretty easily (maybe too easily..). There were some changes which i was not aware on the `master` branch, and i'm not quite sure how that may impact this branch...
manual tests of deployment + verification successfully passed. Pending CI and new changes approval, i think we can merge, and tackle the `inevitable` issues as they come
> The way we verify contracts or create the transaction depends on the factory we use. So just letting anyone use their own factory implementation is not that straightforward imo....