Investigate if transaction can cause network fork/halt

This happened on mainnet. The following transaction was broadcasted. There were two operations in the transaction sidechain_address_delete_operation and sidechain_address_add_operation. The intention was to update the sidechain address by removing it, and then adding it again.

Investigate further, is this the actual cause of the problem, focus on how these two, mutually dependant operations, act in the same transaction, what if we used one transaction for each operation, etc...

Find out this: At the moment of sidechain_address_add_operation execution, when accessing database from sidechain_address_add_operation evaluator, do we see sidechain address as deleted or not.

{
   "ref_block_num":12298,
   "ref_block_prefix":1805427571,
   "expiration":"2022-10-07T09:30:04",
   "operations":[
      [
         115,
         {
            "fee":{
               "amount":0,
               "asset_id":"1.3.0"
            },
            "payer":"1.2.14681",
            "sidechain_address_id":"1.38.45",
            "sidechain_address_account":"1.2.14681",
            "sidechain":"bitcoin"
         }
      ],
      [
         113,
         {
            "fee":{
               "amount":0,
               "asset_id":"1.3.0"
            },
            "payer":"1.2.14681",
            "sidechain_address_account":"1.2.14681",
            "sidechain":"bitcoin",
            "deposit_public_key":"022A555344284F324C19C89AEF4DC62B03A7C5BEA5E3E2559F2F5F7B5D3A051396",
            "deposit_address":"",
            "deposit_address_data":"",
            "withdraw_public_key":"0277B4714A84EFAD0D803B684829782B0EED7FAD20E5F0B0B541F9F92893E60846",
            "withdraw_address":"1MehAHhQfrWSpWKMNjyzBsdJSSiovoy4ut"
         }
      ]
   ],
   "extensions":[
      
   ],
   "signatures":[
      "1f4d682033afbf2db809052f6805892db79f97b66aca2fca66de87833fd2f081f364c9b3d860b82e6a7ed4c24298f56f416594fa4680a62ac93a58709c5a5e87a9"
   ]
}