Add Safe support contract deployments for Stratos Mesos Testnet chain 2047 #1530

Hi Safe team, I am opening this here because the singleton factory side appears complete, but Protocol Kit still cannot use Stratos Mesos Testnet through the default deployment registry.

Related singleton factory issue/PR:

• [New chain]: Stratos Mesos Testnet safe-fndn/safe-singleton-factory#1399
• [New chain]: Stratos Mesos Testnet safe-fndn/safe-singleton-factory#1400

Confirmed working:

1. Singleton factory is deployed on Stratos Mesos Testnet chain id 2047.

eth_getCode(0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7, latest) returns bytecode.

2. A Safe account validates directly on-chain from Mesos RPC.

Command:

scripts/validate-mesos-official-safe-address.sh

Result:

• Chain ID: 2047
• Safe: 0x20Bb0ADa39b5D25f7953d9afE0544007F8954a61
• Version: 1.4.1
• Nonce: 35
• Owners:
  • 0xA638FBA758E0041e8CEF0315BbB33CF516F95c8e
  • 0x3bA46E7D5227e3EA044515c6A352369412E928D1
• Threshold: 2
• Contract code bytes: 171

Blocked behavior:

When I intentionally unset all custom Mesos contractNetworks addresses and run Protocol Kit against chain 2047, it fails before Safe creation/loading with:

Original error: Invalid multiSend contract address

Installed package state:

• @safe-global/protocol-kit@7.1.0
• transitive @safe-global/safe-deployments@1.37.56

I also checked the installed safe-deployments assets locally and chain id 2047 is not present in the v1.4.1 multi_send deployment mapping, which matches the Protocol Kit failure.

Question/request:

Should Stratos Mesos Testnet 2047 Safe support contract mappings, especially multiSend and the related Safe v1.4.1 support contracts, be added to @safe-global/safe-deployments in this repository? Or should Protocol Kit users keep passing explicit contractNetworks for Mesos for now?

Thank you. I can provide the exact Mesos support-contract addresses currently used in my app if that helps.