request to add more debug logs

[bap2pecs]

Context

So I spent lots of time debugging a bridging tx that got stuck.

The API shows

{
    "deposits": [
        {
            "leaf_type": 0,
            "orig_net": 0,
            "orig_addr": "0x0000000000000000000000000000000000000000",
            "amount": "89000000000000000000",
            "dest_net": 1,
            "dest_addr": "0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266",
            "block_num": "195",
            "deposit_cnt": "0",
            "network_id": 0,
            "tx_hash": "0x7918b2970e64e66c78ed936d183b0bb48a0d4bd4c23cf3dbe43287daa0bc44b8",
            "claim_tx_hash": "",
            "metadata": "0x",
            "ready_for_claim": false
        }
    ],
    "total_cnt": "1"
}

The claim_tx_hash of the deposit in the http response is empty. In the server logs I found:

zkevm-bridge-service  | 2024-01-21T03:31:23.544Z        ERROR   claimtxman/claimtxman.go:167        error getting Claim Proof for deposit 0. Error: getting the proof failed, error: height: 31, cur: [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0], error: parentHash: [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0], error: not found in the Storage, network: 0

by following the code, it seems the problem is the data doesn't exist in the mt.rht table when GetClaimProof() is called

it took me a while to realize that I was setting L2PolygonBridgeAddresses incorrectly in the config. I was using the bridge implementation address in the genesis file. Instead, i should be using the proxy address.

Suggestion

The containers logs don't really help much in debugging this issue. I'd suggest adding more logs to help debug such problems in the future