having trouble getting verification bytecode to match etherscan on the larry contract. if anyone has experience dealing with gnarly etherscan verification issues and is willing to help me pls lmk 🙏 

here's a sample. made sure to compile with the same compiler params. 99.9% sure my constructor args are correct

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

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

Solidity Engineer | Researcher | Onchain Degen | DMs Open | https://github.com/0xCooki

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

nw! It shouldn't be this hard still to verify tbqh

yeah i think i must have fucked something up in my original deployment tbh