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
I'm trying to track transfer of the USDY token, A1KLoBrKBde8Ty9qtNQUtq3C2ortoC3u7twggz7sEto6. The getSignaturesForAddress API is not returning all the results I expect.
They're both version 0 transactions. Both transactions reference the signer's Token Account for USDY in the accountKeys list. As far as I can tell, the main difference here is that the first transaction references the USDY token in the Address Lookup Table, but the second does not. When calling getTransaction, I clearly see the USDY token shown in preTokenBalances and postTokenBalances for both txns.
Why might getSignaturesForAddress not show the second txn here, when it clearly interacts with the specified address? Is this a bug?
The text was updated successfully, but these errors were encountered:
I'm trying to track transfer of the USDY token,
A1KLoBrKBde8Ty9qtNQUtq3C2ortoC3u7twggz7sEto6
. ThegetSignaturesForAddress
API is not returning all the results I expect.For example, this transaction shows up in getSignaturesForAddress:
3Ho6c6W4CyidzBaGZ9jYnvJZr4uXkWMk88ZDvN4WZd8difKBHgafjn6DNqJ6uW1pNfVBgnMUcmM19F32Dqos6tnA
But some transactions do not show, such as this one:
5jZYVxqLZkaff6G5fYrrbTvTNtPySqRsr5xG6PXRjU9YQrV72mrzF1txNm9GHr3NbjjEswSaqfmzNAVm4yHXqxBa
They're both version 0 transactions. Both transactions reference the signer's Token Account for USDY in the
accountKeys
list. As far as I can tell, the main difference here is that the first transaction references the USDY token in the Address Lookup Table, but the second does not. When callinggetTransaction
, I clearly see the USDY token shown in preTokenBalances and postTokenBalances for both txns.Why might getSignaturesForAddress not show the second txn here, when it clearly interacts with the specified address? Is this a bug?
The text was updated successfully, but these errors were encountered: