The service README describes Sourcify-compatible verification, and the Standard JSON verification flow (route.verify.ts) is fully implemented with exact/partial match handling.
However, POST /v2/verify/metadata/:chainId/:address and POST /v2/verify/similarity/:chainId/:address currently return 501 not_implemented.
Before working on this, I'd like to confirm scope:
- Is metadata-based verification still intended to be supported, or has the Standard JSON flow superseded it?
- If supported, should the initial scope be limited to Solidity metadata JSON (matching Sourcify's core flow), with similarity matching left out?
- Should the expected response format mirror the existing Standard JSON route (
match, exact_match, creation/runtime fields)?
Happy to put together a scoped implementation (metadata parsing, source extraction, compiler version resolution, reusing existing bytecode match logic) once there's alignment on scope — starting with metadata verification only, leaving similarity matching as a separate follow-up.
The service README describes Sourcify-compatible verification, and the Standard JSON verification flow (
route.verify.ts) is fully implemented with exact/partial match handling.However,
POST /v2/verify/metadata/:chainId/:addressandPOST /v2/verify/similarity/:chainId/:addresscurrently return501 not_implemented.Before working on this, I'd like to confirm scope:
match,exact_match,creation/runtimefields)?Happy to put together a scoped implementation (metadata parsing, source extraction, compiler version resolution, reusing existing bytecode match logic) once there's alignment on scope — starting with metadata verification only, leaving similarity matching as a separate follow-up.