getSignaturesForAddress response order is inconsistent (when the given address has more than one signature in the same block)

[qn-srikanth]

Problem

The following getSignaturesForAddress payload gives inconsistent results.

{
    "jsonrpc": "2.0",
    "id": "my_local_env",
    "method": "getSignaturesForAddress",
    "params": [
      "HbNGeafGRKsXXTcBMCuRoBQpz6bmJ8UyLikuAjc1LCRW",
      {
        "limit": 2,
        "encoding": "jsonParsed"
      }
    ]
  }

---

---

Account : HbNGeafGRKsXXTcBMCuRoBQpz6bmJ8UyLikuAjc1LCRW

Tx signature 1 : 2DQpqgd4oS4iAevswo1wXXJvCaCJm6BPjynYUEPmR79SQgJR3mPJqhgYbRZ4NqMMZT9VxZhQcpiMqrv5jEkjiicm

Tx signature 2 :
vLcnRYGwvt6Mwiq9rGzN6syNFW9aiUPnZN2bqEaFMBA2XxnWAD6q2SPSRqSkgsuo67GjJATs9YR2LN5UjFgTFHt

---

Proposed Solution

This looks like a bug since transaction ordering should be the same. And can lead to incorrect information when extra fields like before, until are used.

[github-actions]

This repository is no longer in use. Please re-open this issue in the agave repo: https://github.com/anza-xyz/agave

[qn-srikanth]

anza-xyz#907