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

Mainnet Release Rehearsal Agent

Show that the deployment script produces exactly the planned state on a mainnet fork before release.

Quality controlRisk managementIT and development
See how it worksGet access
Mainnet Release Rehearsal Agent: what goes in, what the agent does and what you get

What it does

Contract deployments that worked on testnet can fail on mainnet because a step differs, such as a different address, gas cost or role. The agent runs the full deployment script on a mainnet fork and compares the result with the release plan: contract addresses, constructor arguments, ownership, permissions and gas used. It lists every difference and decides which are expected, such as a different chain id, and which are problems. After a fix, it reruns the whole rehearsal until the fork matches the plan. It then writes a rehearsal report for the lead. Edge case: the fork shows a proxy admin owned by the deployer instead of the multisig, so the agent flags it as blocking.

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, continueYes, continueApprovedNoNo 1 STARTS WHEN Release candidate tagged 2 USES A TOOL Spin up a mainnet fork at a recent block 3 USES A TOOL Run the deployment script end to end 4 DOES Read the resulting state: owners, roles, parameters,balances 5 DOES Compare with the release plan and estimate gas 6 CHECKS THE RESULT Does the state match the plan with no blockingdifferences? If not: Report each difference and, if it is a scriptfix, update the script and rerun the rehearsal. Back tostep 3. 7 CHECKS THE RESULT Is gas within the budget and are permissionscorrect? If not: Adjust the script or the plan and rerun. Back tostep 3. 8 USES A TOOL Write the rehearsal report with a diff 9 YOU APPROVE Lead approves the release 10 RESULT Rehearsal report and go or no-go note
Read the steps as a list
  1. Release candidate tagged
  2. Spin up a mainnet fork at a recent block
  3. Run the deployment script end to end
  4. Read the resulting state: owners, roles, parameters, balances
  5. Compare with the release plan and estimate gas
  6. Does the state match the plan with no blocking differences?If not: Report each difference and, if it is a script fix, update the script and rerun the rehearsal. Back to step 3.
  7. Is gas within the budget and are permissions correct?If not: Adjust the script or the plan and rerun. Back to step 3.
  8. Write the rehearsal report with a diff
  9. Lead approves the releaseThe agent waits here for your OK.
  10. Rehearsal report and go or no-go note

How it decides

A rehearsal passes only when addresses, ownership, permissions and parameters match the plan and gas is within the budget. Differences are labeled expected, warning or blocking.

  • Any contract owned by an externally owned address instead of the multisig is blocking
  • Gas more than 10 percent over estimate is a warning
  • A missing role or permission is blocking
  • Two clean rehearsals on different blocks are required for go

Make it yours

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

  • Gas tolerance (default 10 percent)
  • Number of clean rehearsals required (default 2)
  • Chains and forks used
  • Differences classed as expected

What keeps you in control

It always asks you first

  • Lead approves the release after reading the report

Hard limits

  • Never deploys to mainnet
  • Never edits the release plan without recording the change

It stops when

  • Done: two clean rehearsals and go approved
  • Stop: blocking difference persists after three reruns, so the lead decides

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 happensOn the Tuesday rehearsal, the fork showed the proxy admin owned by the deployer, a blocking difference. The agent updated the script to transfer ownership to the multisig and reran. The second run matched on 18 of 18 checks, but gas was 14 percent over, so it adjusted batching and reran. Both checks passed on two blocks and the lead approved the release.

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