Verify contract

Publish the original sources and build settings of a deployed contract from your own toolchain.

Contract address

Optional: fills the address into the commands below.

Let your agent handle verification

Paste this into your coding agent from the contract’s repository. It finds the toolchain and uses your original deployment settings.

Agent prompt

Verify an already deployed contract using this repository's original sources and build settings.

Network: Elysium Testnet
Chain ID: 99801
Contract address: Find it in the deployment records for this chain; ask me if the target is ambiguous.
Blockscout verification API: https://elysium.kinetiq.xyz/api/

1. Detect Foundry or Hardhat and the installed tool/plugin version. Locate the contract identifier and original deployment artifacts. Reuse the exact compiler version, optimizer settings, EVM version, via-IR setting, build profile, constructor arguments and linked library addresses. If artifacts are missing, compile using those original settings and the deployment's build profile before verification. Ask for missing information; do not guess or change the source to force a match.
2. Use the existing RPC configuration if needed and confirm its chain ID. The explorer URL is not an RPC endpoint. Do not print credentials or ask for a wallet private key.
3. For Foundry, run forge verify-contract ADDRESS PATH:CONTRACT --chain 99801 --verifier blockscout --verifier-url https://elysium.kinetiq.xyz/api/ --watch. Supply ABI-encoded constructor arguments where needed and use the original Foundry profile.
4. For Hardhat 3 with hardhat-verify 3.x, configure chainDescriptors[99801].blockExplorers.blockscout with url https://elysium.kinetiq.xyz and apiUrl https://elysium.kinetiq.xyz/api, then run npx hardhat verify blockscout --network NETWORK ADDRESS with the original build profile and constructor arguments. For Hardhat 2, use the compatible hardhat-verify 2.x plugin with etherscan.customChains pointing to this API, a non-secret apiKey placeholder, and the verify task. Preserve other networks, plugins and compiler settings; do not upgrade the project to another major version.
5. Verification publishes the selected contract sources and dependencies. Submit only the necessary source/build data. This endpoint does not require an API key. Do not redeploy or broadcast transactions.
6. Wait for the final result. If indexing is delayed, retry with a bounded wait. If verification fails, report the exact mismatch or missing input. An accepted submission or a partial source match is not full verification. If the tool skips an existing partial match, use --skip-is-verified-check for Foundry or --force for Hardhat with the original build. Confirm the result at https://elysium.kinetiq.xyz/testnet-explorer/address/ADDRESS?tab=contract.