Skip to main content

v1.8.3 Mainnet Release Packet

Canonical live release packet for the v1.8.3 Base mainnet broadcast completed on 2026-04-11.

Release target: v1.8.3

Post-Release Checkpoint (2026-04-11)​

  • Head commit: c12b8796
  • CI status on main: Tests, Docs Drift, and Security scanning all green (latest run window at 2026-04-11T15:46Z)
  • Go-live checkpoint tag: release-v1.8.3-golive-2026-04-11c
  • Live health probes:
    • https://4626.fun/api/health returned 200 with success: true, db.ok: true, and supabase.ok: true
    • https://keepr.4626.fun/readyz returned 200 with status: "ready"

Live Base Infra Addresses​

ContractAddress
CreatorRegistry0x9D86e8FAfA39527c4FE13AAa8FBD2B424f9f65Fb
CreatorOVaultFactory0xC7E919899Fd4C0C4f6f4269a63046107f85848bB
VaultActivationBatcher0x7Cc0050842433968cc7A0884d192b61FD0b46F63
CreatorLotteryManager0xd593A8A58BDf7E7448D2dAbDE0Ae3B2BAFDA1357
CreatorVRFConsumerV2_50xdd25Ed1b3D258Ccc6D306a9a325Af1A7F96C7F47
SolanaBridgeAdapter0x90F578A4e23c1cB8DDFE63fd496ED7F4474f2b00
UniversalBytecodeStoreV20xA009B1Bf8cB711c115d832AEb392156BA6A4112e
UniversalCreate2DeployerFromStore0xFd2657b6f1905C3F0494942F618a68963CF792Ec
CreatorOVaultCoreModule0xeD728378f969f8e94a19fC081172D1e67B80412e
CreatorOVaultStrategiesModule0x0f1A26b93AD56BBbC5e0486A920621944FF6ABd6
CreatorOVaultAdminModule0xFC40e9768eeaAE634CBD2A72DA0CF809d3c908e0
DeploymentBatcher0xcDbEeB764df9878ebAFbf101cc818370f703bC4F
DeploymentBatcherPhase3Helper0xF185Cb60E108E324f67e75cf8106B8e9950c16ed
DeploymentBatcherUniV4Helper0xfe1C5eaa76942208298f510c820e7E8328f6d031

DeploymentBatcherPhase3Helper and DeploymentBatcherUniV4Helper are constructor-created children of DeploymentBatcher, not standalone top-level broadcasts.

Broadcast Summary​

The live rollout executed in two phases from the clean broadcast worktree that reproduced deployments/base/v1.8.3-bytecode-manifest.json:

  1. shared/global contracts via script/DeployInfrastructure.s.sol
  2. deterministic v2 CREATE2 layer via script/deploy-base-full-release.sh

Both phases were broadcast by 0xB05Cf01231cF2fF99499682E64D3780d57c80FdD.

The deterministic v2 pass used the canonical base-release:* salt tags for v1.8.3. Canonical tag list and deterministic wiring details are maintained in CREATE2 Registry.

Broadcast Transactions​

Shared/Global Layer​

ContractAddressTx HashBlockTimestamp
CreatorRegistry0x9D86e8FAfA39527c4FE13AAa8FBD2B424f9f65Fb0x6edd4308a5c2070b68d0faf556f2e2585c9b9a86d6e5c05343337060d1129224445446832026-04-11T03:38:33Z
CreatorOVaultFactory0xC7E919899Fd4C0C4f6f4269a63046107f85848bB0x9a4549d128d1538f00002fc94f9ee034b198259933eef5d633b828b79b5f2b72445446832026-04-11T03:38:33Z
VaultActivationBatcher0x7Cc0050842433968cc7A0884d192b61FD0b46F630xec000b9048601fcf0b6a2a7642f6c83aa2185b11338e0ce5810b45cd9bee716c445446832026-04-11T03:38:33Z
CreatorLotteryManager0xd593A8A58BDf7E7448D2dAbDE0Ae3B2BAFDA13570xe226c9fd94caa94a0d83ce19d61c8830b410f21c24cbbe177e0bad8c605d449d445446832026-04-11T03:38:33Z
CreatorVRFConsumerV2_50xdd25Ed1b3D258Ccc6D306a9a325Af1A7F96C7F470x002d57e9438b08d4fd74a84a45e2e0a3b01b52d83d18b5c079eebe65ae312e47445446832026-04-11T03:38:33Z
SolanaBridgeAdapter0x90F578A4e23c1cB8DDFE63fd496ED7F4474f2b000x4452e12dc59aacf1f035490a4eadb6bc21f920d778d9dd84712fb8359d06ab71445446832026-04-11T03:38:33Z

Deterministic V2 Layer​

ContractAddressTx HashBlockTimestamp
UniversalBytecodeStoreV20xA009B1Bf8cB711c115d832AEb392156BA6A4112e0x55c08632a3fa5029d59d1eceb88215b83cf86539fb9553dcef748cde30642d90445446922026-04-11T03:38:51Z
UniversalCreate2DeployerFromStore0xFd2657b6f1905C3F0494942F618a68963CF792Ec0xdb72ef666c40b8ad51c39a2cf580bf0af75e879e42c213552504d662a0e5b1e8445446922026-04-11T03:38:51Z
DeploymentBatcher0xcDbEeB764df9878ebAFbf101cc818370f703bC4F0xc1a1f6f9a5e57cfef6cbeb1b339a56b765f0cbbe81aaace9c77cd0d32cc18f0b445446922026-04-11T03:38:51Z
DeploymentBatcherPhase3Helper0xF185Cb60E108E324f67e75cf8106B8e9950c16ed0xc1a1f6f9a5e57cfef6cbeb1b339a56b765f0cbbe81aaace9c77cd0d32cc18f0b445446922026-04-11T03:38:51Z
DeploymentBatcherUniV4Helper0xfe1C5eaa76942208298f510c820e7E8328f6d0310xc1a1f6f9a5e57cfef6cbeb1b339a56b765f0cbbe81aaace9c77cd0d32cc18f0b445446922026-04-11T03:38:51Z

DeploymentBatcherPhase3Helper and DeploymentBatcherUniV4Helper were created inside the DeploymentBatcher constructor, so they share the same transaction, block, and timestamp as the parent batcher.

Manifest Artifacts​

  • Bytecode / codeId manifest: deployments/base/v1.8.3-bytecode-manifest.json
  • Current live deployment snapshots: deployments/base/contracts/**/*.json
  • Previous live release packet: docs/operations/deployment/releases/v1.8.2-mainnet.md

The clean broadcast worktree that reproduced this manifest used these pinned local helper repos:

  • lib/solidity-lib at 3fcc8ee6d5c7dea3283416cbcee601d89504a243
  • lib/v3-core at e3589b192d0be27e100cd0daaf6c97204fdb1899
  • lib/v3-periphery at 80f26c86c57b8a5e4b913f42844d4c8bd274d058

Representative v1.8.3 code IDs are unchanged from v1.8.2; use deployments/base/v1.8.3-bytecode-manifest.json as the source of truth and docs/reference/current-contract-inventory.md for the canonical published index.

Repo Cutover Defaults​

The repo now points its canonical Base defaults at the live v1.8.3 addresses:

  • .env.example
  • frontend/.env.example
  • frontend/src/config/contracts.defaults.ts
  • docs/reference/addresses.md
  • docs/reference/current-contract-inventory.md
  • deployments/base/contracts/**/*.json

Release-version defaults also remain pinned to v1.8.3 for deploy session and Telegram helpers.

Verification Notes​

  • Onchain deployment succeeded for the shared/global layer and deterministic v2 layer, and the repo defaults/snapshots now match the live v1.8.3 addresses.
  • DeploymentBatcher constructor dependencies resolved to UniversalBytecodeStoreV2=0xA009B1Bf8cB711c115d832AEb392156BA6A4112e, UniversalCreate2DeployerFromStore=0xFd2657b6f1905C3F0494942F618a68963CF792Ec, CreatorOVaultCoreModule=0xeD728378f969f8e94a19fC081172D1e67B80412e, CreatorOVaultStrategiesModule=0x0f1A26b93AD56BBbC5e0486A920621944FF6ABd6, and CreatorOVaultAdminModule=0xFC40e9768eeaAE634CBD2A72DA0CF809d3c908e0.
  • DeploymentBatcher BaseScan verification failed after the live CREATE2 deployment because the explorer reported Compiled contract deployment bytecode does NOT match the transaction deployment bytecode.
  • Forge's automatic verification step also did not verify the shared/global broadcasts during the live run because it reported no matching bytecode for those phase-1 transactions.
  • Root-cause status: the live DeploymentBatcher tx payload matches local salt || initcode exactly after the 32-byte CREATE2 salt prefix, and onchain runtime only differs from the local deployed bytecode at immutable-reference slots. The mismatch is therefore not a bad broadcast or constructor-arg drift; it is an explorer verification-path limitation for this deployment shape.
  • Canonical forensic verification command for this release:
scripts/ops/verify-deployment-batcher-forensic.sh \
  --tx 0xc1a1f6f9a5e57cfef6cbeb1b339a56b765f0cbbe81aaace9c77cd0d32cc18f0b \
  --batcher 0xcDbEeB764df9878ebAFbf101cc818370f703bC4F
  • Operational policy: treat DeploymentBatcher as forensically matched but explorer-unverified for v1.8.3; do not spend more operator time on repeat BaseScan retries unless explorer behavior changes.

Dependency Advisory Exception​

  • elliptic (low, GHSA-848j) remains in the tree via LayerZero V2 tooling (@layerzerolabs/oapp-evm → ethers@5). There is no patched release on npm. We accept this for LZ V2 bridge compatibility with the constraint that production services do not execute the ethers v5 / hardhat JS tooling. Tracking: docs/audits/npm-advisories-triage.md and issue #227.