Content
@
0 reply
0 recast
2 reactions
Matt Solomon
@msolomon.eth
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
2 replies
2 recasts
15 reactions
frangio
@frangio
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.
1 reply
0 recast
1 reaction
Matt Solomon
@msolomon.eth
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
1 reply
0 recast
1 reaction
Matt Solomon
@msolomon.eth
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
2 replies
0 recast
0 reaction
frangio
@frangio
Have you found this approach to help with that? I always imagined the difficulty to provide feedback came from the fact that at the end you will have two pieces of bytecode, and if they don't match there isn't much you can say about the cause.
1 reply
0 recast
0 reaction
jonwalch
@jonwalch
json bad
0 reply
1 recast
0 reaction
