bug: proxy: Error detecting settled GER (step 3/WaitL1SettledGER)

[joanestebanr]

Bug Report

version: v0.11.0-rc7

This issue is very likely that is going to be fixed at the same time as this issue: #1817

If the step WaitL1SettledGER doesn't have a UpdateL1InfoTree event, then next step WaitingGERInjection is not able to find the injected GER.

You can reproduce it in bali (L2(63) -> L2(82):

curl http://localhost:8080/tracker/v1/network/63/tx/0xd1cceffc0734f1db6bda982d9b4699a8c39ac243bfd11eca532f0183bd5918f8 | jq .

        "has_verify_batches_trusted_aggregator": true,
        "has_update_l1_info_tree": false,
        "has_update_l1_info_tree_v2": false

{
  "tracking_status": "running",
  "claim_status": "pending",
  "network_id": 63,
  "tx_hash": "0xd1cceffc0734f1db6bda982d9b4699a8c39ac243bfd11eca532f0183bd5918f8",
  "bridge_status": {
    "bridge_type": "L2->L2",
    "block_number": 45774079,
    "log_index": 1,
    "block_timestamp": 1787316446,
    "event": {
      "leaf_type": "Asset",
      "origin_network": 63,
      "origin_address": "0x0000003f0000003f0000003f0000003f0000003f",
      "destination_network": 82,
      "destination_address": "0x43377b45c0e92257588f092b461c2496fc5053b3",
      "amount": "450000000000000",
      "deposit_count": 36102
    }
  },
 (...)
    {
      "step_index": 2,
      "step_name": "CertificatePending",
      "status": "done",
      "start_date": "2026-09-14T13:07:31.925507518Z",
      "end_date": "2026-09-14T13:07:31.925507518Z",
      "result": {
        "certificate_id": "0xe772f1c39ed1752998d7187023dd97d02044592302437b0d2e2d63eb8b82e9c7",
        "status": 4,
        "status_string": "Settled",
        "settlement_tx_hash": "0x1a95ce62b0fb605b7782a82727809c9e3df4e1a33eaafb9f0f519b29d46159f1",
        "block_number": 11703046,
        "block_timestamp": 1789390836
      }
    },
    {
      "step_index": 3,
      "step_name": "WaitL1SettledGER",
      "status": "done",
      "start_date": "2026-09-14T13:07:31.925507518Z",
      "end_date": "2026-09-14T13:07:31.925507518Z",
      "result": {
        "tx_hash": "0x1a95ce62b0fb605b7782a82727809c9e3df4e1a33eaafb9f0f519b29d46159f1",
        "settlement_block_number": 11703046,
        "settlement_block_timestamp": 1789390836,
        "settlement_log_index": 166,
        "ger": "0xd83ca04f64f9c684bede2a6b56a461993b20842b3eb3effcf16c5657c00abddf",
        "ger_block_number": 11702957,
        "ger_block_timestamp": 1789389696,
        "ger_log_index": 218,
        "l1_info_tree_index": 357845,
        "has_verify_batches_trusted_aggregator": true,
        "has_update_l1_info_tree": false,
        "has_update_l1_info_tree_v2": false
      }
    },
    {
      "step_index": 4,
      "step_name": "WaitingGERInjection",
      "status": "inProgress",
      "start_date": "2026-09-14T13:07:31.925507518Z"
    },
    {
      "step_index": 5,
      "step_name": "WaitingL1InfoLeafAvailable",
      "status": "pending"
    },
    {
      "step_index": 6,
      "step_name": "WaitingClaim",
      "status": "pending"
    },
    {
      "step_index": 7,
      "step_name": "Claimed",
      "status": "pending"
    }
  ],
  "error": null
}

[joanestebanr]

The point is that the proxy is not able to known exactly to which certificate was included the bridge (agglayer only give us information about last certificate). So could be that the last certificate submitted doesn't update L1InfoTree because there are no new leaf