You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: Currently, we don't include the status in the feeder.Transaction struct. However, it is present in the response from the feeder gateway (example). This isn't a problem for us since we calculate the status on the fly in the rpc handler, but it could be a problem for developers who import the feeder package.
Solution: include all fields present in the feeder gateway response in the feeder.Transaction struct. We need to make the changes below.
With 0.12.1, the status enum is changing to include RECEIVED, REJECTED, REVERTED, ACCEPTED_ON_L2, ACCEPTED_ON_L1
Two more status enums are being added (related to #881):
Problem: Currently, we don't include the status in the
feeder.Transaction
struct. However, it is present in the response from the feeder gateway (example). This isn't a problem for us since we calculate the status on the fly in the rpc handler, but it could be a problem for developers who import the feeder package.Solution: include all fields present in the feeder gateway response in the
feeder.Transaction
struct. We need to make the changes below.With 0.12.1, the status enum is changing to include
RECEIVED
,REJECTED
,REVERTED
,ACCEPTED_ON_L2
,ACCEPTED_ON_L1
Two more status enums are being added (related to #881):
execution_status
:REJECTED
,REVERTED
,SUCCEEDED
finality_status
:RECEIVED
,ACCEPTED_ON_L2
,ACCEPTED_ON_L1
The text was updated successfully, but these errors were encountered: