Hi @programskillforverification thanks for your PR!

Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

Hi @programskillforverification thanks for your PR!

Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

hey @programskillforverification ! will you be able to push this PR over the finish line? alternatively we can take it over

Hi @programskillforverification thanks for your PR!
Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

hey @programskillforverification ! will you be able to push this PR over the finish line? alternatively we can take it over

I am sorry that I forget this pr. I will finish it asap.

Hi @programskillforverification thanks for your PR!

Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

Install command also belongs to verify. According to our community, it's better that "have forge verify-contract do forge install too". Or split this pr into two, one is for verify, the other is for script.

Hi @programskillforverification thanks for your PR!
Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

Install command also belongs to verify. According to our community, it's better that "have forge verify-contract do forge install too". Or split this pr into two, one is for verify, the other is for script.

hey @programskillforverification what @zerosnacks suggests is to externalize code from crates/verify/src/install.rs into it's own crate / commons and reuse in both install and verify, does this make sense? @zerosnacks pls chime in in case I I got your comment wrong. thanks

Hi @programskillforverification thanks for your PR!
Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

Install command also belongs to verify. According to our community, it's better that "have forge verify-contract do forge install too". Or split this pr into two, one is for verify, the other is for script.

hey @programskillforverification what @zerosnacks suggests is to externalize code from crates/verify/src/install.rs into it's own crate / commons and reuse in both install and verify, does this make sense? @zerosnacks pls chime in in case I I got your comment wrong. thanks

hey @programskillforverification ! Bump on the previous message, would you be able to take this PR over the finish line, otherwise happy to take over / assign to someone else. just let us know

Hi @programskillforverification thanks for your PR!
Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

Install command also belongs to verify. According to our community, it's better that "have forge verify-contract do forge install too". Or split this pr into two, one is for verify, the other is for script.

hey @programskillforverification what @zerosnacks suggests is to externalize code from crates/verify/src/install.rs into it's own crate / commons and reuse in both install and verify, does this make sense? @zerosnacks pls chime in in case I I got your comment wrong. thanks

hey @programskillforverification ! Bump on the previous message, would you be able to take this PR over the finish line, otherwise happy to take over / assign to someone else. just let us know

I will finish right now

Hi @programskillforverification thanks for your PR!
Instead of moving the install command into the verify folder where it arguably does not belong it may make more sense to split it out into its own individual crate.

Install command also belongs to verify. According to our community, it's better that "have forge verify-contract do forge install too". Or split this pr into two, one is for verify, the other is for script.

hey @programskillforverification what @zerosnacks suggests is to externalize code from crates/verify/src/install.rs into it's own crate / commons and reuse in both install and verify, does this make sense? @zerosnacks pls chime in in case I I got your comment wrong. thanks

Hey, @grandizzy, do you means move to crates/common? I once try but can't solve cyclic package dependency