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

Introducing the Cove alpha release: Simple, reliable, open-source contract verification.

Test it out now at https://covecontracts.com

Learn more: https://twitter.com/msolomon44/status/1688656321053425664

Security at Optimism. Formerly built Umbra and more at ScopeLift

I assume you don't support JSON input because one of the main goals is to match to a git commit?

It would be useful to support it as it's a universal interface that all toolchains should be able to generate. Perhaps you can match the contents in the JSON file against the files in the repo.

That's a good idea which makes it easier to support other langs/frameworks—take JSON + repo data, verify that the paths+remappings in the JSON match the repo, then compile from JSON

Part of the reason we avoided JSON (in addition to ensuring a commit hash) is that it's what everyone already does and it seems to work poorly for verification (whether this is a problem with the JSON itself or tooling providers or verification providers is another question), so figured we'd try something different