Today, if an l1_handler transaction is rejected, there is no way for the sender to know why it failed other than manually computing the associated l1_handler transaction hash and querying its status. This endpoint basically does that for the user, by starting from the sending l1 transaction, and returning the status of all associated l1_handler transactions on Starknet (a single L1 transaction can send multiple messages)
Today, if an l1_handler transaction is rejected, there is no way for the sender to know why it failed other than manually computing the associated l1_handler transaction hash and querying its status. This endpoint basically does that for the user, by starting from the sending l1 transaction, and returning the status of all associated l1_handler transactions on Starknet (a single L1 transaction can send multiple messages)
This change is