Content
@
0 reply
0 recast
0 reaction
Varun Srinivasan
@v
Someone asked in the conference what Foundry improvements would be helpful. A big one that we're struggling with today when deploying FC contracts is producing TS ABIs from the Foundry artefacts.
2 replies
0 recast
4 reactions
gakonst
@gakonst
What's a TS ABI? Any examples in mind?
1 reply
0 recast
0 reaction
Varun Srinivasan
@v
High level problem is that sometimes verification fails (due to quirks of Etherscan or w/e) and we want a valid ABI object to copy paste, but there are lots of little gotchas that don't work today. I think @horsefacts.eth has some ideas he wants to contribute here, once we're done with the OP mainnet migration
2 replies
0 recast
0 reaction
gakonst
@gakonst
Can't you just "cat abi | jq"? Or forge inspect?
1 reply
0 recast
3 reactions
horsefacts 🚂
@horsefacts.eth
ah yeah, the "forge inspect abi" formatter works nicely for this.
1 reply
0 recast
2 reactions
gakonst
@gakonst
Yeah exactly
1 reply
0 recast
2 reactions
horsefacts 🚂
@horsefacts.eth
Turns out I was also looking for the --show-standard-json-input flag to forge verify-contract. Once again, the tools I need already exist. Our main issue was that scripts skip Etherscan verification for contracts that are "Similar Match" verified. Needed to generate and upload the full compiler input to fully verify.
0 reply
0 recast
4 reactions
