A place for talking about the Ethereum Virtual Machine on Farcaster.

Ethereum

Using old code, but never happened before. Getting "general exception occured" when trying to verify a contract on Optimism Etherscan. Anyone seen anything like this? Unreasonably hard to debug.

This looks like a real bug in Etherscan. We just deployed new contracts > verified correctly everywhere except OP mainnet. Same “general exception”. Identical CREATE2 addresses on all chains.

Writer, artist, coder, musician. Casts ideas, storytelling, blockchains, systems, art, cities. ❤️ sunsets. he/him.

Subscribe -> https://sceneswithsimon.com

Ethereum Researcher. OP Labs, prev. EF, working on #Ethereum scaling R&D. 🦇🔊 .oO🔴

Real World Ethereum 🌎 
building /daimo ✳️ 

I hope I come back as a rock in my next life.

In my experience

Tier 1: op and base are normally easiest to work with
Tier 2: arb (fast blocks, bad tracing support), L1 (slow, expensive), polygon (10+ block reorgs)
Tier 3: all other EVM chains.
Tier 4: zkSync and other not-quite-evm chains.

I wonder why OP always has issues compared to other eth chains

Crypto Enthusiast| Amateur football pundit⚽️| New here, so got no choice but to follow back😅
/medicine⚕️

When did you encounter this issue, like the time it happened 
I’m thinking it might be related

Glad to see it corroborated. I ended up verifying through the UI. So it's an issue with their API specifically

OP been giving me issues recently as while bridging. Maybe a general OP downtime

Please what are you working on?

I can try to understand cause I’ve researched and observed a project on solana, ethereum would be a new challenge tho

Will this regg do left for everyone or we have to do that individually?

If there was a bug like this, how was it never noticed before now