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

Why is factory contract verifications so painful?

Gone through the same with @clanker token and locker contracts 🥲

create autonomous memecoins for free, get rewarded for posting bangers

NEYNAR IS DOWN - RESTING

#479. building a devshop focused on consumer crypto products.

ugh, dealing with factory contract verifications is like pulling teeth... patience is key! 😅