Corn Network Delisting

The queued Safe transactions do not cut off every USDT0 route involving Corn. Rootstock has no reachable Safe transaction-service entry in the workbook and the Rootstock OFT still has peers(30331) set to Corn's OFT. The fork validation also shows Rootstock can still send to Corn after applying the current transaction set. The Corn Safe row only returns a stale no-calldata transaction at nonce 94 while the Safe nonce is 97. It does not remove any OFT peers. Corn's OFT still has outbound peers configured, including Ethereum, Rootstock, XLayer and Plasma. The Corn fork test confirms the existing send behavior to another USDT0 chain remains usable.

This contradicts the stated requirement that Corn be cut off on every USDT0 chain. If other chains remove Corn as a peer while Corn or Rootstock still allow sends, users can initiate transfers on routes that the decommissioning is meant to disable.

Add and execute current-nonce Safe transactions for Rootstock and Corn before approving the removal set. Rootstock should remove CORN_EID as an OFT peer, matching the other non-Plasma chains. Corn should either remove all remote USDT0 peers or otherwise block outgoing sends so users cannot initiate transfers from Corn after the cutoff.