Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for blockchain developers

Explorer Source Verification Agent

Get every deployed contract verified on the explorer with source that matches the deployed bytecode.

Quality controlAutomationIT and development
See how it worksGet access
Explorer Source Verification Agent: what goes in, what the agent does and what you get

What it does

After a contract is deployed, the explorer page shows only bytecode until the source is verified, and mismatched compiler settings make verification fail in confusing ways. The agent takes the deployed address, compiles the source with the recorded settings, and compares the resulting bytecode with what is on chain. If they match, it submits verification and checks the explorer status. If it fails, it changes one setting at a time, such as optimizer runs, compiler version or constructor arguments, and tries again. It reports which settings worked. The developer approves publishing. Edge case: bytecode differs only in the metadata hash, so the agent treats it as a match and says so.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedYes, continueNoNo 1 STARTS WHEN Deployment finishes 2 USES A TOOL Collect addresses, source and recorded compilersettings 3 USES A TOOL Compile the source with the recorded settings 4 DOES Compare compiled bytecode with deployed bytecode 5 CHECKS THE RESULT Does the bytecode match? If not: Change one setting (compiler version, optimizerruns, constructor arguments) and recompile. Back to step3. 6 YOU APPROVE Developer approves publishing the source 7 USES A TOOL Submit verification to the explorer 8 USES A TOOL Check the verification status 9 CHECKS THE RESULT Is the contract shown as verified? If not: Adjust the submission format or settings andretry. Back to step 7. 10 RESULT Verification record per contract
Read the steps as a list
  1. Deployment finishes
  2. Collect addresses, source and recorded compiler settings
  3. Compile the source with the recorded settings
  4. Compare compiled bytecode with deployed bytecode
  5. Does the bytecode match?If not: Change one setting (compiler version, optimizer runs, constructor arguments) and recompile. Back to step 3.
  6. Developer approves publishing the sourceThe agent waits here for your OK.
  7. Submit verification to the explorer
  8. Check the verification status
  9. Is the contract shown as verified?If not: Adjust the submission format or settings and retry. Back to step 7.
  10. Verification record per contract

How it decides

It submits verification only when compiled bytecode matches on chain bytecode, ignoring the metadata hash. If not, it tries documented setting changes one at a time and records each attempt.

  • Ignore the metadata hash when comparing bytecode
  • Try settings in a fixed order and record each try
  • Stop after 8 attempts per contract
  • Proxies are verified with their implementation and linked

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Maximum attempts per contract (default 8)
  • Explorers to submit to
  • Order of settings to try
  • Whether to verify proxies and implementations together

What keeps you in control

It always asks you first

  • Developer approves publishing the source

Hard limits

  • Never publishes source the developer has not approved
  • Never changes source code, only settings

It stops when

  • Done: all contracts verified and recorded
  • Stop: attempt limit reached, so the developer gets the log

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensThree contracts were deployed. Two verified on the first try. The vault contract failed because the optimizer runs were 200 in the config but 1,000 at deploy. The agent changed that single setting, recompiled and the bytecode matched. The explorer first said pending, then verified on the second status check. The developer approved publishing and all three showed as verified.

More agents for blockchain developers

Quality control · Product development

Product Documentation Task Test Agent

Docs examples that work exactly as written.

8 steps2 checks3 jobs
Decisions · IT and development

Blockchain Use Case Feasibility Screen Agent

A fair, documented screen of a blockchain proposal with a clear recommendation

10 steps2 checks6 jobs
Coding · Quality control

Test Coverage Gap Closing Agent

Add tests to the riskiest untested code and prove that they catch real bugs

10 steps2 checks11 jobs
Risk management · Quality control

Contract Static Analysis Triage Agent

Find the real vulnerabilities among analyzer output and confirm each with a test

11 steps2 checks2 jobs