Contract verification on XDCScan just got a lot less painful. We now accept multi-part metadata submissions — the standard compilation output you get from Hardhat and Foundry — alongside the existing single-file and standard-json flows.
Why it matters
Most real-world contracts aren’t a single file. Until now, verifying a multi-file project meant flattening sources or hand-assembling a standard-json input, which is where verification attempts usually died. With multi-part verification you upload your sources as-is, tell us the entry file and compiler version, and we compile against the exact dependency graph your toolchain produced.
How to use it
- Open any unverified contract on xdcscan.io.
- Choose Verify & Publish, then the multi-part option.
- Upload your
.solsources, pick the compiler version and EVM target, and submit.
Verified contracts get full source browsing, read/write contract interaction, and — because our AI insight engine can now see what your code actually does — human-readable decoding of your contract’s transactions and events instead of raw hex.
Verification is also available programmatically through the API v2 endpoints documented at xdcscan.io/api-docs, so you can wire it into your deployment pipeline.