warp-update-extend

name	warp-update-extend
description	Add a new chain to an existing warp route owned by a customer. Reads a Linear ticket, adds the new chain to the deploy.yaml, builds a customer-specific strategy file for existing chains, runs warp apply, and outputs transaction files for the customer to sign via their multisig.

Warp Route Extension

You are adding a new chain to an existing Hyperlane warp route. Routes are commonly owned by the customer via a Gnosis Safe on ethereum with ICAs on the other EVM chains — but the owner set is open: a route may have no ethereum leg, or be owned by Squads (SVM), a Starknet account, a Cosmos multisig, etc. Don't assume the ethereum-Safe-plus-ICA model; resolve the actual owner per chain. You will deploy the new chain contracts with a deployer key, and generate transaction files for existing chains that the customer must sign.

Run Log (mandatory)

Maintain the durable, per-ticket run log per /warp-run-log — that skill owns the storage contract (Linear-document-by-title primary, single-writer discipline, local-file fallback), the machine-row + prose entry shape, and the surface-the-URL-as-proof hard gate. Use warp-update-extend as the skill name in each prose entry, and do not report this skill complete until the run-log URL has been surfaced.

Log at least: (a) skill entry with the ticket ID + warp route ID + the new chain, (b) every [CONFIRM:] gate — before and after the response, (c) the new-chain contract deploy (deployed addresses + tx hashes), (d) the warp apply run for existing chains, (e) the emitted customer transaction-file paths (one per signer/chain), (f) skill exit (success or bail-out). Log smooth steps too — success data grounds the retrospective as much as failure data.

Input

The user provides:

• Linear ticket URL or ID (required, e.g. ENG-3516)

If missing, ask now.

Key Context (Prerequisite)

This skill runs warp apply to extend a warp route to a new chain. It needs a deployer key matching the new chain's protocol to sign the new-chain deployment txs. It auto-loads ~/.hyperlane/key-contexts/<ticket-id>.yaml produced by /warp-deploy-select-keys. If the artifact does not exist, invoke /warp-deploy-select-keys <ticket-id> first.

For each unique protocol touched by the extension (typically just the new chain's protocol, but warp apply may also need to sign on existing chains when re-applying their state), read keys.<protocol>.name and keys.<protocol>.source from the artifact. Expand <KEY_<PROTOCOL>_VALUE> placeholders in the commands below per the canonical key-value expansion legend in /warp-key-value-expansion.

Ownership model (read before Step 5/6)

The deployer key plays TWO distinct roles in a chain extension; do not confuse them:

1. Deploy signer — signs the deployment txs on the new chain (contract bytecode + initial proxy setup). The deployer transiently holds ownership during the deploy phase, for the lifespan of those few txs.
2. Initial-owner-transfer signer — in the same warp apply run, signs the transferOwnership(<customer-ICA-or-Safe>) tx that moves the new contract's ownership to the customer's chosen owner. This is executed by the deployer's jsonRpc submitter atomically with the deploy.

Implications for deploy.yaml:

• The new chain's owner field in deploy.yaml is always the customer's ICA or Safe (per Step 5). It is never the deployer address.
• The customer never signs anything on the new chain during the extension — the deployer signs deploy + transferOwnership for them. The customer only signs on existing chains (per the strategy file in Step 7).

This is the opposite of the initial-deploy flow (/warp-deploy-init-route), where deploy.yaml carries the deployer as temporary owner and a separate /warp-deploy-update-owners run later transfers to the real owner. For extensions of routes already owned by a customer, the transfer happens atomically.

---

Step 1: Fetch the Linear Ticket

Fetch the ticket per /fetch-linear-ticket, then read the new-chain extension details from the returned description.

---

Step 2: Extract Extension Details

Parse the ticket to extract:

Field	Description
Existing warp route ID	e.g. USDC/igra — look for "warp route ID" or derive from token + chain names
New chain(s) to add	The chain(s) being added to the route
Token details	Symbol, decimals, name — usually carried from existing route
Customer's ethereum Safe	The multisig that owns the route on ethereum
Customer's ICA addresses	Per-chain ICA addresses if the ticket lists them
Owner type	Whether existing chains are owned by a Safe directly or via ICAs

Ask the user to clarify anything ambiguous.

---

Step 3: Find Existing Route Files

Locate the existing deploy.yaml and config.yaml in the registry:

REGISTRY_PATH="$(pwd)/../hyperlane-registry"
ls "$REGISTRY_PATH/deployments/warp_routes/<TOKEN>/"

Read both files and show the user:

• Existing chains and their types
• Contract addresses (from config.yaml)
• Current owner addresses per chain

Identify all existing chains — these are the ones the customer controls and for which we need to generate transaction proposals.

---

Step 4: Look Up Mailbox for New Chain

REGISTRY_PATH="$(pwd)/../hyperlane-registry"
cat "$REGISTRY_PATH/chains/<new-chain>/addresses.yaml" | grep "^mailbox:"

For Sealevel chains, also look up the IGP from rust/sealevel/environments/mainnet3/<chain>/core/program-ids.json.

Tron address note: Tron uses base58 T... addresses externally (e.g., TronScan, user-provided), but the Hyperlane contracts and deploy.yaml use EVM hex 0x... format internally. Tron is EVM-like (isEVMLike() = true). Always convert any Tron base58 address to hex before putting it in deploy.yaml:

python3 -c "
import base58, sys
addr = base58.b58decode_check(sys.argv[1])
print('0x' + addr[1:].hex())
" TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
# → 0xa614f803b6fd780986a42c78ec9c7f77e6ded13c

This applies to: token address, mailbox address, owner address — anything going into deploy.yaml for Tron.

---

Step 5: Determine Owner for the New Chain

The new chain's contract must be owned by the customer from the start — never use the deployer address as owner. Match the customer's existing ownership structure.

Case A — Customer uses ICAs on non-ethereum chains (most common):

This ICA path is for an EVM (or Tron) new chain. get-owner-ica.ts filters to Ethereum-protocol chains and silently drops Sealevel/Cosmos/Starknet/etc. — if the new chain is non-EVM, it returns no address with no error. For a non-EVM new chain, take the owner from the ticket's native owner (e.g. a Squads multisig on SVM), not from this script; do not proceed on an empty ICA result.

The new chain needs an ICA owned by the customer's ethereum Safe. Run without --deploy first to compute the address deterministically, confirm it looks right, then re-run with --deploy to create it on-chain (ICAs are permissionless — anyone can deploy one):

cd typescript/infra

# Dry-run first (no gas spent):
pnpm tsx scripts/keys/get-owner-ica.ts \
  --environment mainnet3 \
  --ownerChain ethereum \
  --owner <CUSTOMER_ETHEREUM_SAFE> \
  --chains <new-chain>

# Then deploy:
pnpm tsx scripts/keys/get-owner-ica.ts \
  --environment mainnet3 \
  --ownerChain ethereum \
  --owner <CUSTOMER_ETHEREUM_SAFE> \
  --chains <new-chain> \
  --deploy

This prints the ICA address. Use it as the owner for the new chain in deploy.yaml.

Signer disclosure — --deploy does NOT use the per-ticket selected key. get-owner-ica.ts --deploy takes no key argument; it signs the ICA-deployment tx with the environment's shared Role.Deployer (via config.getMultiProvider()), not the protocol key this skill otherwise uses. ICAs are permissionless and the derived address is independent of who deploys, so this is safe — but disclose it at the [CONFIRM:] gate (the ICA deployment is signed by the shared mainnet3 deployer, not the selected key) and confirm before running --deploy. (Wiring the selected key is tracked as follow-up code work.)

Tron ICA deployment caveat: On Tron, get-owner-ica.ts may fail with invalid BytesLike value — see Tron-specific notes at the bottom.

Tron TRX funding: The deployer key needs ≥ 1000 TRX before any Tron transaction — see Tron-specific notes.

Case B — Customer owns directly with a Safe per chain (no ICAs):

Use the customer's Safe address on the new chain directly as owner. Ask the user for that address if the ticket doesn't list it.

Ask the user which case applies if not clear from the ticket.

---

Step 6: Add New Chain to deploy.yaml

Update the existing deploy.yaml to add the new chain. The new chain is almost always synthetic.

Standard synthetic addition:

<new-chain>:
  decimals: <decimals> # from existing route
  mailbox: '<mailbox-address>'
  name: <token-name>
  owner: '<customer-ica-or-safe-address>'
  symbol: <token-symbol>
  type: synthetic

If the new chain is Tron (collateral):

tron:
  decimals: <decimals> # typically 6 for USDT
  mailbox: '<mailbox-address-in-0x-hex>' # convert from base58 if needed
  name: <token-name>
  owner: '<customer-ica-address-in-0x-hex>' # EVM hex, not base58
  scale: <scale-factor-if-needed> # e.g. 1000000000000 if bridging to 18-decimal chain
  symbol: <token-symbol>
  token: '<token-contract-in-0x-hex>' # MUST be EVM hex, not Tron base58
  type: collateral

If the new chain is Sealevel (solanamainnet, eclipsemainnet):

<new-chain>:
  decimals: <9-if-18-decimals-collateral-else-match>
  gas: 300000
  hook: '<igp-address-from-program-ids.json>'
  mailbox: '<mailbox-address>'
  metadataUri: 'https://raw.githubusercontent.com/hyperlane-xyz/hyperlane-registry/main/deployments/warp_routes/<TOKEN>/metadata.json'
  name: <token-name>
  owner: '<customer-owner-address>'
  symbol: <token-symbol>
  scale: <10^(collateral_decimals - 9) if collateral decimals > 9, else omit>
  type: synthetic

Rules:

• Only append the new chain — do NOT modify any existing chain entries
• Alphabetical sort, both levels per /registry-yaml-sort-policy — that skill carries the canonical deploy.yaml key order. Insert the new chain at its alphabetical position among the top-level entries (do NOT append at the top or bottom), and keep the keys within the new entry alphabetical (re-sort the inline template above if you edit it). CI blocks unsorted PRs.
• Copy decimals, name, symbol from existing entries
• owner is always the customer's ICA or Safe address from Step 5 — never the deployer

Write the updated deploy.yaml back to the registry. Show the user the diff (new chain entry only), then end your message with this marker (this MUST be the very last thing in your message):

[CONFIRM: Proceed with deploy.yaml extension for <new-chain>]

Do not proceed until confirmed.

---

Step 7: Build the Customer Strategy File

Determine the customer's ownership structure from Step 2 and the existing deploy.yaml owners.

Output strategy file: ~/.hyperlane/strategies/<customer-name>-strategy.yaml (Derive <customer-name> from the ticket/token/customer — e.g. moonpay, nexus, eni)

Strategy structure depends on owner type:

If customer uses ICAs on non-ethereum chains (most common pattern):

The ethereum chain has a Gnosis Safe. All other chains have ICA submitters routing through that Safe.

ethereum:
  submitter:
    type: gnosisSafeTxBuilder
    chain: ethereum
    version: '1.0'
    safeAddress: '<CUSTOMER_ETHEREUM_SAFE>'

<chain1>: # existing non-ethereum chain
  submitter:
    type: interchainAccount
    chain: ethereum
    destinationChain: <chain1>
    owner: '<CUSTOMER_ETHEREUM_SAFE>'
    internalSubmitter:
      type: gnosisSafeTxBuilder
      chain: ethereum
      safeAddress: '<CUSTOMER_ETHEREUM_SAFE>'

# ... repeat for all existing chains except the NEW chain
# Do NOT add the new chain to the strategy — it's deployed directly with our key

Do NOT include the new chain in the strategy. The strategy covers only existing chains (owned by customer). The new chain is deployed with our deployer key.

If the route has a fee contract with a separate fee Safe (common for AW-managed routes):

Some routes have a tokenFee.feeContracts section in deploy.yaml with a separate owner (the AW fee Safe). Add a feeSubmitter to each chain entry — it mirrors the main submitter structure but uses the fee Safe address instead.

The fee Safe ethereum address is in typescript/infra/config/environments/mainnet3/governance/safe/warpFees.ts (ethereum entry = 0x8Ff4c563f26db00e65bD93d9f662A51c304C09b0). Per-chain ICA addresses (what goes in feeContracts[chain].owner in deploy.yaml) are in typescript/infra/config/environments/mainnet3/governance/ica/warpFees.ts. These are different: deploy.yaml uses the ICA address per chain, the strategy feeSubmitter uses the ethereum Safe as the controlling account.

ethereum:
  submitter:
    type: gnosisSafeTxBuilder
    chain: ethereum
    version: '1.0'
    safeAddress: '<CUSTOMER_ETHEREUM_SAFE>'
  feeSubmitter:
    type: gnosisSafeTxBuilder
    chain: ethereum
    version: '1.0'
    safeAddress: '<FEE_SAFE>'

<chain1>:
  submitter:
    type: interchainAccount
    chain: ethereum
    destinationChain: <chain1>
    owner: '<CUSTOMER_ETHEREUM_SAFE>'
    internalSubmitter:
      type: gnosisSafeTxBuilder
      chain: ethereum
      safeAddress: '<CUSTOMER_ETHEREUM_SAFE>'
  feeSubmitter:
    type: interchainAccount
    chain: ethereum
    destinationChain: <chain1>
    owner: '<FEE_SAFE>'
    internalSubmitter:
      type: gnosisSafeTxBuilder
      chain: ethereum
      safeAddress: '<FEE_SAFE>'

The fee submitter generates a separate combined Safe TX Builder bundle for the fee Safe (distinct from the customer's main bundle).

If customer has a Solana/Sealevel chain:

Add a file submitter for that chain — the transactions will need to be executed by the customer using their Solana tooling:

solanamainnet:
  submitter:
    type: file
    chain: solanamainnet
    filepath: /tmp/<customer>-solanamainnet-txs.json

If the new chain is also ICA-owned:

If in Step 5 we deployed a new ICA for the customer on the new chain, still do NOT include the new chain in the strategy. The new chain's contracts don't exist yet — warp apply deploys them with the deployer key and atomically transfers ownership to the customer's ICA in the same run (per the Ownership model section at the top of this skill). No separate post-deploy ownership-transfer pass is needed.

Write the strategy file.

---

Step 8: Load Keys from the Key-Context Artifact

Read keys.<protocol>.name and keys.<protocol>.source from ~/.hyperlane/key-contexts/<ticket-id>.yaml for every protocol touched by the extension. Do NOT ask the user for env var names inline — the artifact is the source of truth (see the "Key Context (Prerequisite)" section at the top of this skill).

---

Step 9: Run Warp Apply

9a: Start the HTTP Registry

Start it per /start-http-registry with --writeMode. Note the port and the background task ID — needed to stop it after this step.

9b: Build and Show the Command

The command runs from typescript/cli. Expand <KEY_<PROTOCOL>_VALUE> per the artifact's source field (see the canonical key-value expansion legend in /warp-key-value-expansion). Supply --key.<protocol> for the new chain's protocol — the deployer signs its deploy + atomic ownership transfer; don't assume that's ethereum (existing chains are handled through the strategy's submitters, not a direct key):

# --key.<new-chain-protocol> is the new chain's protocol: ethereum / sealevel / cosmos / tron / starknet / radix / aleo
pnpm --silent -C typescript/cli hyperlane warp apply \
  --registry http://localhost:<port> \
  --key.<new-chain-protocol> <KEY_<PROTOCOL>_VALUE> \
  --strategy ~/.hyperlane/strategies/<customer>-strategy.yaml \
  --receipts-dir /tmp/<customer>-<warp-route-id>-txs \
  -w <WARP_ROUTE_ID> \
  --yes

Key flag rule: NEVER combine --key (legacy) with --key.<protocol>. Use --key.<protocol> for the protocol(s) you're signing. Using both --key and --key.tron will error: "make sure to use --key.{protocol} or the legacy flag --key but not both".

Tell the user:

Starting warp apply to extend <WARP_ROUTE_ID>. This deploys contracts on <new-chain> and generates transaction proposals for existing chains. Existing chains requiring customer signature: <list> New chain being deployed: <new-chain>

End your message with this marker (this MUST be the very last thing in your message):

[CONFIRM: Run warp apply to extend route to <new-chain>]

9c: Run the Command

Run it from typescript/cli. Show full output on completion.

On success: the CLI deploys new contracts and writes tx proposal files to the receipts-dir.

After success — verify the transferOwnership calls match the expected pattern:

grep -r "transferOwnership" /tmp/<customer>-<warp-route-id>-txs/

This grep matches EVM receipts only. If the new chain is non-EVM (SVM/Cosmos/etc.), its atomic post-deploy transfer is not an EVM transferOwnership call, so the grep won't match it — verify that chain's owner via warp check (it reads the chain's own owner state) instead of this string search.

Two distinct expectations (per the Ownership model section at the top of this skill):

• New chain's owner transfer — verification is protocol-specific:
  • EVM / Tron new chain: its jsonRpc receipt should contain transferOwnership(<customer-ICA-or-Safe-from-Step-5>) — the deployer's atomic post-deploy transfer to the customer. Confirm the target address matches Step 5's resolved ICA / Safe.
  • Non-EVM new chain (Sealevel / Cosmos / Starknet / …): the transfer is not an EVM transferOwnership call and won't appear in the grep. Verify the new chain's owner directly via warp check (it reads the chain's own owner state) and confirm it equals Step 5's resolved owner.
• Existing chains' receipt files should NOT contain ANY transferOwnership calls. Existing-chain ownership is already where it should be; the extension does not change it.

If either expectation is violated — transferOwnership to the deployer address anywhere, or transferOwnership calls targeting existing chains — the deploy.yaml owner fields were corrupted (typically by a previous run hitting the runWarpRouteApply corruption bug; see the Notes section). Stop immediately — do not send these files to the customer. To fix:

1. Restore correct ICA owners in deploy.yaml for existing chains (check git history for original values)
2. Confirm the new chain's owner field is the customer's ICA / Safe (not the deployer address)
3. Restart the HTTP registry and re-run warp apply

On failure: stop the HTTP registry and show the error. Common issues:

• Deployer key not funded → run /warp-deploy-fund-deployer first
• Strategy chain not in config → verify all existing chains appear in the strategy
• ICA not deployed → go back to Step 5 and deploy the ICA

9d: Stop the HTTP Registry

Stop the background task noted in 9a per /stop-http-registry. Always stop it, even on failure.

9e: Fork-Simulate-Verify Before Shipping (mandatory)

The customer tx files are pending multisig execution (the customer signs later), so validate them up front per the /warp-verify-onchain-config contract's Mode B before handing them off. If the customer files are a single flat EVM tx file, invoke /warp-route-check with the warp route ID + that file: it forks each chain, impersonates the customer's Safe / ICA owners, replays the batch calldata from those addresses, self-relays ICA messages, and runs hyperlane warp check on the fork against the target deploy.yaml. Otherwise, take the UNSUPPORTED path in the outcomes below — do not invoke it on a format it can't consume.

Fail-closed caveat: per /warp-verify-onchain-config, /warp-route-check today only consumes a single flat EVM transactions file — not a receipts directory, a Safe-object batch, or an SVM batch. An extension whose customer files are a directory / Safe-object / SVM batch cannot be fork-verified by the current implementation: do NOT report it fork-verified — surface the files for manual verification and rely on the post-execution registry-PR CI, until the part-2 warp-route-check rework. Only a single-file EVM batch is fork-authoritative today.

• PASS (EVM single-file fork check ran clean) → proceed to Step 10 and ship the files.
• FAIL → do NOT ship: the batch would leave the route misconfigured once signed. Surface the violations, fix the deploy.yaml / strategy, and re-run Step 9.
• UNSUPPORTED → the customer files are a directory / Safe-object / SVM batch the fork gate can't consume (per the caveat above). Do NOT invoke /warp-route-check on them and do NOT report fork-verified. Decode the batch's calldata and verify manually that it produces the target config, then end your message with a [CONFIRM: Manually verified <batch> matches target — ship the files] gate. Only ship after the human confirms; the post-execution registry-PR CI is the remaining check.

(The real-chain confirmation happens after the customer executes — via the registry PR CI in Step 11.)

---

Step 10: Collect TX Files and Send to Customer

10a: Find the Output Files

The strategy submitters write transaction proposals to the receipts-dir:

ls -la /tmp/<customer>-<warp-route-id>-txs/

For gnosisSafeTxBuilder: the output JSON is a Safe Transaction Builder batch importable to the Gnosis Safe UI (https://app.safe.global → Apps → Transaction Builder → Import).

For interchainAccount submitter: generates one separate Safe TX Builder JSON per destination chain, all with chainId: "1" (all destined for the ethereum Safe). The customer must import and execute each file separately — they are NOT combined into one file.

For file submitter: raw transaction JSON for that chain.

New chain receipt file is NOT for the customer: The <new-chain>-jsonRpc-*.json file contains transactions that were already executed directly by the deployer key during warp apply (e.g. setting destination gas on the new contract). Do NOT send this to the customer.

Show the user the full path of each output file and clarify which ones go to the customer.

10b: Summarize Deployment Results

Show the user:

1. New contracts deployed (from the warp apply output):

   Chain	Contract Type	Address
   <new-chain>	HypSynthetic	0x...

2. Transaction files for customer (in receipts-dir):

   File	Chain(s)	Action Required
   ethereum-txs.json	ethereum + ICA chains	Import to Safe UI and sign
   solanamainnet-txs.json	solanamainnet	Execute using Solana tooling

3. What the customer transactions do:

   • enrollRemoteRouter on existing chain contracts to recognize the new chain
   • (If ICA was just deployed) Initialize the new ICA on each destination

---

Step 11: Registry PR (Extension)

After the customer executes their transactions and the route is live, update the registry:

11a: Update config.yaml

The warp apply run should have updated the config.yaml with the new chain's deployed address. Verify:

cat $REGISTRY_PATH/deployments/warp_routes/<TOKEN>/<file>-config.yaml

If it wasn't updated (e.g., due to registry write failures), manually add the new chain's contract address to config.yaml following the existing format.

11b: Commit and Open PR

First write the changeset per /add-registry-changeset — bump minor (a new chain is added to the published route), summary in past tense (e.g. "extended <WARP_ROUTE_ID> to <new-chain>"). A registry PR without a changeset is blocked by the merge bot. Then commit the changed files + changeset together. Scope git add to the exact changed files — never the whole deployments/warp_routes/<TOKEN>/ directory (it can pull in other routes' files or API-keyed writeMode RPC artifacts) and never git add .:

cd $REGISTRY_PATH
git checkout -b feat/extend-<TOKEN>-<new-chain>
# exact files only: the route's deploy.yaml + config.yaml (config.yaml gained the new chain's addresses)
git add deployments/warp_routes/<TOKEN>/<chains>-deploy.yaml deployments/warp_routes/<TOKEN>/<chains>-config.yaml .changeset/<changeset-file>
git status   # confirm nothing unexpected is staged
git commit -m "feat: extend <WARP_ROUTE_ID> to <new-chain>"
git push -u origin HEAD

gh pr create \
  --base main \
  --title "feat: extend <WARP_ROUTE_ID> to <new-chain>" \
  --body "$(cat <<'EOF'
## Summary

Extends the `<WARP_ROUTE_ID>` warp route to `<new-chain>`.

| Field | Value |
| ----- | ----- |
| **Linear** | <linear-issue-url> |
| **Warp route ID** | `<WARP_ROUTE_ID>` |
| **New chain** | `<new-chain>` |
| **Customer Safe** | `<safe-address>` |

### New contracts deployed

| Chain | Contract | Address |
| ----- | -------- | ------- |
| `<new-chain>` | `HypERC20` / `HypSynthetic` | `0x...` |

### ICAs deployed

| Chain | ICA Address | Owner Safe |
| ----- | ----------- | ---------- |
| `<new-chain>` | `0x...` | `<safe-address>` |

### Customer action required

The customer must sign and execute the transaction proposals in:
- `<path-to-txs-file>`

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Show the user the PR URL.

---

Notes

• The registry path is $(pwd)/../hyperlane-registry from the monorepo root.
• The strategy file covers only existing chains (customer-owned). The new chain uses the deployer key directly.
• gnosisSafeTxBuilder output is importable to Gnosis Safe UI: Apps → Transaction Builder → "Import".
• interchainAccount submitter generates one file per destination chain (all chainId: "1", all for the ethereum Safe) — NOT a single bundled file.
• If the customer has an apiKey for the Safe (from the strategy yaml pattern in nexus-strategy.yaml), ask if they need it included.
• The file submitter for Sealevel chains writes raw transactions — the customer executes these with their Solana CLI or tooling.
• After this skill, run /warp-deploy-register-route once the registry PR is merged to update warpIds.ts and agent config.
• warp apply re-runs corrupt deploy.yaml owners (bug, fixed in monorepo): runWarpRouteApply previously set ALL chain owners to the deployer in intermediateOwnerConfig and wrote that back to the registry — meaning a second run would generate transferOwnership(deployer) for every existing chain. The fix scopes this override to new chains only. If working with an older CLI, always check for unexpected transferOwnership calls after running (see Step 9c).
• Multi-RPC failure modes on the new-chain deploy: a stale-gas OOG on initialize, or a confirmation-timeout on a tx that already landed (status: 1), are read-after-write / short-confirmation-budget artifacts, not real failures. Apply the same cushions a fresh deploy uses — pin a single premium RPC for opstack/multi-RPC chains, and/or raise estimateBlockTime in the local registry metadata for short-block chains (ethereum, bsc, tron), then restore per the cleanup gate. Full mechanism in /warp-deploy-init-route §8c.

Tron-specific notes

• Tron is EVM-like: same deployer key (EVM private key) works, standard ICA scripts work.
• Always use EVM hex 0x... in deploy.yaml — never Tron base58 T.... Passing a base58 address to ethers.js causes invalid address error.
• Convert base58 → hex: python3 -c "import base58, sys; a = base58.b58decode_check(sys.argv[1]); print('0x'+a[1:].hex())" <TRON_ADDR>
• Deployer needs ≥ 1000 TRX before any Tron transaction (feeLimit cap in TronWallet.ts).
• If get-owner-ica.ts --deploy fails on Tron with invalid BytesLike value, it's a TronWallet.buildContractCall bug — write a custom script calling triggerSmartContract with individually typed params and feeLimit: 15_000_000.