feat: add base (Base mainnet) deploy env and bootstrap release#27
Merged
Conversation
Add a deployment.json for the new zeus 'base' environment (Base mainnet) and a v1.2.0-base-init bootstrap release so the shared v1.3.0-usdc-credits release can deploy USDCCredits on the fresh chain. - script/deploys/base/deployment.json: Base mainnet env config using the mainnet-alpha multisig/billing addresses, native USDC token, and the shared treasury. VERSION 0.0.0 (fresh chain). - script/releases/v1.2.0-base-init: deploys a ProxyAdmin owned by the ops multisig and advances the env 0.0.0 -> 1.2.0 so v1.3.0-usdc-credits (gated from: 1.2.0) chains afterward. Run order on base: v1.2.0-base-init (0.0.0 -> 1.2.0) then v1.3.0-usdc-credits (1.2.0 -> 1.3.0).
mcclurejt
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the new zeus
baseenvironment (Base mainnet) and a bootstrap release so the existingv1.3.0-usdc-creditsrelease can deployUSDCCreditson the fresh chain.Why a bootstrap release is needed
v1.3.0-usdc-creditsdeploys its proxy against an existingProxyAdminand is gatedfrom: "1.2.0":A brand-new
baseenv has noProxyAdminand sits atVERSION 0.0.0, sov1.3.0cannot run on its own. The newv1.2.0-base-initrelease bootstraps the chain and advances the env to1.2.0sov1.3.0-usdc-credits(from: 1.2.0) chains afterward.Changes
script/deploys/base/deployment.json— Base mainnet env config.mainnet-alpha(executorMultisig,computeOpsMultisig,computeWhitelisterMultisig,billingAdmin).USDC_TOKEN=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913(native USDC on Base mainnet).USDC_TREASURY=0x83fa243203f1B9B4F0D2806154095Cd765b9cA21(same treasury used onmainnet-alpha).USDC_MINIMUM_PURCHASE=1000000,VERSION=0.0.0(fresh chain).script/releases/v1.2.0-base-init/— bootstrap release (0.0.0 → 1.2.0).1-deployProxyAdmin.s.sol— EOA deployer that deploys aProxyAdmin, transfers ownership tocomputeOpsMultisig, and registers it in the zeus Env. Modeled onv0.1.0-base-sepolia-initbut deploys only theProxyAdmin(USDCCredits is left tov1.3.0).upgrade.json—name: base-init, single EOA phase.Resulting run order on
basev1.2.0-base-init(0.0.0 → 1.2.0) — creates theProxyAdmin.v1.3.0-usdc-credits(1.2.0 → 1.3.0) — deploysUSDCCreditsagainst thatProxyAdmin. Shared release left untouched.Testing
forge buildpasses (only the pre-existing unrelated lint warning intest/AppController.t.sol).forge fmtapplied to the new script.Notes for reviewers
v1.2.0-base-init, itsupgrade.jsonto, and thefrom: 1.2.0gate of the sharedv1.3.0-usdc-creditsall line up so the chain is contiguous.v1.3.0-usdc-creditsfiles.