-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Description
Hello everyone !
Summary
Our archive node misses some txs on txs query endpoint, they should appear since we see that metadata matches the query
I tried to play with different filters and offset/limit without success
Steps to Reproduce
Query:
Notice that the tx appears by hash:
https://cosmoshub4.coin.ledger.com/cosmos/tx/v1beta1/txs/9B97D967178AAEC011CB6C2D1722734E1D571E809C23ECB1AD4C3F5939C74859
And by blockheight:
https://cosmoshub4.coin.ledger.com/cosmos/tx/v1beta1/txs?query=tx.height%3D21367773
On another node (public) I noticed the same behavior:
https://rest.cosmoshub-main.ccvalidators.com/cosmos/tx/v1beta1/txs?query=transfer.recipient=%27[…]it=500&pagination.offset=0&pagination.reverse=true
On nodes without archive we can see that it's a different response (expected):
https://cosmos-rest.publicnode.com/cosmos/tx/v1beta1/txs/9B97D967178AAEC011CB6C2D1722734E1D571E809C23ECB1AD4C3F5939C74859
Expected Behavior
9B97D967178AAEC011CB6C2D1722734E1D571E809C23ECB1AD4C3F5939C74859 should be returned by https://cosmoshub4.coin.ledger.com/cosmos/tx/v1beta1/txs?query=transfer.recipient=%27cosmos1n50eg56cayurl3s6shlt52ryctrgc92jcpv7ah%27&pagination.limit=100&pagination.offset=0&pagination.reverse=true
Cosmos sdk version
v0.53.4
See: https://cosmoshub4.coin.ledger.com/cosmos/base/tendermint/v1beta1/node_info
Did we miss anything or it's an actual issue ? Indexing or sdk ?
Thanks for your time.