Stephan
@stephancill
verified it. for those interested - i ended up downloading all the solidity files from the token creator contract, - compiled with parameters that exactly match that of the creator contract, - ran forge verify-contracts with the --show-standard-json-input and saved it to an output.json - used the output.json for verification on etherscan with some fake constructor args - obtained the real constructor args by getting the diff between the generated bytecode and deployed bytecode - used the real args to verify https://basescan.org/address/0xB3A720f17902b7d2e8c38c5044C3B20e8AC9C27C#code
6 replies
5 recasts
31 reactions
Samuel ツ
@samuellhuber.eth
@gakonst is there a foundry update coming for easier verification of factory contracts and their deployed contracts?
1 reply
0 recast
1 reaction
gakonst
@gakonst
could u open an issue for this? we can investigate
1 reply
0 recast
2 reactions
Samuel ツ
@samuellhuber.eth
Cc @0xbhaisaab can you document the issues on GitHub ?
1 reply
0 recast
1 reaction
0xbhaisaab
@0xbhaisaab
I have still not have done a proper investigation on that. it always kept throwing bytecode not matched error. Still cannot confidently call out if it's a foundry problem, basescan problem or something else all together.
0 reply
0 recast
1 reaction
