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
The current implementation of GetTxByHash returns a TX object, which contains no metadata whatsoever about the tx's status on the chain. Is it in the chain? How much gas did it use? What height did it get in at?
All of these questions could be answered by the amino endpoint, currently none of them can be found in the gRPC response.
Problem Definition
Most users who are requesting a transaction by hash do not only want the full transaction but also wish to know it's status on the chain. This is why the same info in amino and on eth returns this info in addition to just the transaction data itself.
Proposal
The endpoint should return a new struct TxInfo (or whatever name best fits convention) that contains metadata about the transaction status and the Tx object itself as a field.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
The current implementation of GetTxByHash returns a TX object, which contains no metadata whatsoever about the tx's status on the chain. Is it in the chain? How much gas did it use? What height did it get in at?
All of these questions could be answered by the amino endpoint, currently none of them can be found in the gRPC response.
Problem Definition
Most users who are requesting a transaction by hash do not only want the full transaction but also wish to know it's status on the chain. This is why the same info in amino and on eth returns this info in addition to just the transaction data itself.
Proposal
The endpoint should return a new struct TxInfo (or whatever name best fits convention) that contains metadata about the transaction status and the Tx object itself as a field.
For Admin Use
The text was updated successfully, but these errors were encountered: