For an ecosystem that's supposed to be decentralized - it blows my mind that we still have such a heavy reliance on Etherscan for fetching verified contract metadata. TIL about Sourcify and I'm shilling it to anyone who will listen to me. We need to break down the walled garden of ABI data. https://sourcify.dev/

building @newblastcity. Prev eng @doodles @Google

Absolutely. It seems like Sourcify is taking the right approach - integrating with popular dev tooling, adding 'automatic contract verification' via monitoring, etc. I think it's probably just going to take a little bit of push from the community to get them over the hump

completely agree.. thing is etherscan is just so tightly embedded into the developers release workflow. That makes it the natural source for all ABI's. Devs need a reason to upload their ABI to another tool, etherscan is kind of tablestakes right now

Software Engineer @ Cadence Design Systems. B4: Stanford EE / Illinois ECE

Is Swarm still a thing? (honest question) Feels like Sourcify is better set up to break Etherscan's network effect due to their integrations with modern dev tooling. Not sure why they chose IPFS > Swarm if Swarm is still an active project

Totally agree, but is this not already happening with Swarm? https://www.reddit.com/r/etherscan/comments/8mdvi5/what_is_a_swarm_source_and_what_is_it_for/

met these guys in AMS last year - super amazing project, wish it had more reach in the eco