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
@ninabarbakadze recently did some phenomenal work on feat: add TxStatus rpc endpoint. This preliminary work indexed committed transactions so users could see that they were committed in a lightweight manner and not need to rely on BroadcastTxCommit or the Tx endpoint + the kv_indexer.
As part of providing greater tracing ability for users transactions is to modify the TxStatus endpoint such that it gives the current status of the transaction. They can be as follows:
Unknown(default case)
Pending (in the mempool)
Committed (in the secondary index in the block store)
Rejected (as decided by the mempools rejected cache
Evicted (has been kicked out of the mempool because of a TTL or not a high enough fee)
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:
Feature Request
Summary
@ninabarbakadze recently did some phenomenal work on feat: add TxStatus rpc endpoint. This preliminary work indexed committed transactions so users could see that they were committed in a lightweight manner and not need to rely on
BroadcastTxCommit
or theTx
endpoint + thekv_indexer
.As part of providing greater tracing ability for users transactions is to modify the
TxStatus
endpoint such that it gives the current status of the transaction. They can be as follows:Unknown
(default case)Pending
(in the mempool)Committed
(in the secondary index in the block store)Rejected
(as decided by the mempools rejected cacheEvicted
(has been kicked out of the mempool because of a TTL or not a high enough fee)For Admin Use
The text was updated successfully, but these errors were encountered: