Skip to content

Latest commit

 

History

History
41 lines (27 loc) · 1.59 KB

File metadata and controls

41 lines (27 loc) · 1.59 KB

App Chain Upgrades

Table of Contents

1. Overview

There are two possible workflows for app chain upgrades. The parameter registry admin address can be controlled:

  1. by a local private key, or
  2. by Fireblocks.

The goals for testnets are minimal friction, whilst still proving out the Fireblocks approval process before mainnet.

2. Claude Code

You can use Claude Code to orchestrate the multi-step upgrade process including bridge finalization. The /xmtp-upgrade skill handles repo validation, signing mode selection, and verification automatically:

/xmtp-upgrade upgrade GroupMessageBroadcaster on testnet-dev

3. Environment Defaults

Environment Default To Override
testnet-dev WALLET ADMIN_ADDRESS_TYPE=FIREBLOCKS
testnet-staging WALLET ADMIN_ADDRESS_TYPE=FIREBLOCKS
testnet FIREBLOCKS ADMIN_ADDRESS_TYPE=WALLET
mainnet FIREBLOCKS No override possible

Add the override variable to your command when you need to use the non-default signing method.

4. Choose Your Workflow

  • wallet.md - Private key signing (simpler upgrade process)
  • fireblocks.md - Fireblocks signing (multi-step upgrade process)