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
7 replies
5 recasts
24 reactions
Stephan
@stephancill
shoutout @cooki for the hint!!
1 reply
1 recast
9 reactions
karan
@defikaran.eth
@0xbhaisaab the pain is real
1 reply
0 recast
2 reactions
Jack Dishman
@dish
would be cool if you guys added the deployer address, FID, cast hash, and img on the erc20 !
0 reply
0 recast
2 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
Cooki
@cooki
omg lol π
0 reply
0 recast
1 reaction
KMacπ β© γ
@kmacb.eth
ππ
0 reply
0 recast
0 reaction
Henry
@hlau
Have a variation of this problem. I think I might have updated foundry in between deploys and sadly cleaned out the cache. I was able to get the contract verified during deployment, which can be seen here: https://sepolia.basescan.org/address/0x0e8c93541c119eef5e7a0ce4cfec53ff2675c2a3 but the deployed bytecode differs by 53 chars and it's not an exact match for this: https://basescan.org/address/0xE86a4f763A9E63C57AA84Ce6eC091f248150aBD5
1 reply
0 recast
0 reaction
