payloads to remove botanix

[shankars99]

Note on payload sizes: the mesh is a full pairwise mesh (every network is directly peered with every other, not just hub-and-spoke), so Botanix's batches have ~5x more transactions than any other chain's — each of Botanix's 6 OApp contracts needs one call per other chain (6×5=30), while every other chain only needs one call per contract targeting Botanix (6).

1. Stop new messages from being created (set send uln to blocked uln)

npx hardhat lz:sdk:unwire --target-network botanix-mainnet --phase send-block --generate-payloads --ci --signer 0x0000000000000000000000000000000000000001

npx hardhat lz:sdk:payloads-to-safe \
  --input "payloads/unwire-payloads-send-block-botanix-mainnet-*.json" \
  --name "Botanix removal - Stage 1: block send" \
  --description "Points sendLibrary at BlockedMessageLib on all Botanix<->X pathways, both directions. Stops new messages; safe with anything already in flight." \
  --prefix stage1-send-block

2. Make sure that all messages that are sent out of into botanix are complete

npx ts-node scripts/check-inflight-messages.ts --target-network botanix-mainnet

3. Stop incoming messages (set receive uln to blocked uln)

npx hardhat lz:sdk:unwire --target-network botanix-mainnet --phase receive-block --generate-payloads --ci --signer 0x0000000000000000000000000000000000000001

4. Unpeer botanix

npx hardhat lz:sdk:unwire --target-network botanix-mainnet --phase unpeer --generate-payloads --ci --signer 0x0000000000000000000000000000000000000001

npx hardhat lz:sdk:payloads-to-safe \
  --input "payloads/unwire-payloads-receive-block-botanix-mainnet-*.json,payloads/unwire-payloads-unpeer-botanix-mainnet-*.json" \
  --name "Botanix removal - Stage 3+4: block receive + unpeer" \
  --prefix stage3-4-receive-unpeer