/cosmos/tx/v1beta1/txs endpoint's pagination issue

[BenWolfaardt]

Summary of Bug

When searching for transactions above a certain height, as recommended in issue #10448, the resulting limit is applied, however, the pagination isn't working as the "next_key": null which is not the expected return.

If you could please kindly take a look at this it'll be greatly appreciated.
​

Request

​

GET https://api.cosmos.network/cosmos/tx/v1beta1/txs?events=tx.height>=8294900&pagination.limit=10&order_by=ORDER_BY_DESC

​

Response

​

{
  "txs": [
    ...
  ],
  "tx_responses": [
    ...
  ],
   "pagination": {
        "next_key": null,
        "total": "220"
    }
}

Similar Issues

• #10448
• #10506

Version

Cosmos SDK v0.42.6 (Gaia v5.0.2 / cosmoshub-4)

Steps to Reproduce

Perform the above-outlined steps.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[aleem1314]

Try pagination.offset=10 instead of pagination.key. The SDK simply proxies /cosmos/tx/v1beta1/txs request to Tendermint and it only supports pagination with offset.

[BenWolfaardt]

Thank you @aleem1314 for your suggestions. We've been able to successfully implement them and achieve that which we wanted to.

Kind regards,