Elysium

Verify contract

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

Optional: fills the address into the commands below.

Let your agent handle verification

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://testnet.elysium.kinetiq.xyz/api/verify

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://testnet.elysium.kinetiq.xyz/api/verify --skip-is-verified-check --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://testnet.elysium.kinetiq.xyz and apiUrl https://testnet.elysium.kinetiq.xyz/api/verify, 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, an apiKey placeholder (not a secret), 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. It accepts verification only: it refuses reads such as getabi and getsourcecode. 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 Hardhat skips an existing partial match, use --force with the original build. Confirm the result at https://testnet.elysium.kinetiq.xyz/address/ADDRESS?tab=contract.