rpc call to get transactions given an address

[roccomuso]

Problem

what's the RPC to get the list of transactions given an address?

I saw getConfirmedSignaturesForAddress2 but I don't want only the list of signature, instead I'd like to get some basic info like amount received/sent and addresses involved. Something more verbose.

I assumed having the signatures and call getConfirmedTransaction would give me the txs details, but what if I want the timestamp of the tx instead of the slot?
Nesting rpc calls seems a wrong approach to me.

[CriesofCarrots]

Oops, duplicate issues. solana-labs/solana-web3.js#992 I'll close the other

Right now chaining those calls (getConfirmedSignaturesForAddress2 and getConfirmedTransaction) is the way to go. getBlockTime will return the timestamp from the slot

[roccomuso]

I saw that getBlockTime could have issues depending on the validator: #12413

[roccomuso]

Do you know if there are planned improvements to allow pagination on getConfirmedSignaturesForAddress2 ?
For pagination I mean keeping a "cursor" that allow to filter out old transactions (the opposite of "before" parameter).
Instead of the before parameter an after parameter would do the job.

[CriesofCarrots]

Yes! There is actually already an until parameter enabled on the RPC side. I just filed an issue about getting that exposed in the web3.js sdk: #12417

[roccomuso]

Oh thanks, that's a lot useful! I guess also the documentation must be updated.

[CriesofCarrots]

Oh thanks, that's a lot useful! I guess also the documentation must be updated.

💯 on my list for today

[roccomuso]

Wouldn't be also useful to get rid of the upper limit of 1000 txs ?

[CriesofCarrots]

I think we'll keep that limit for now. RPC isn't optimized for huge data dumps.

[roccomuso]

Any plan to aggregate those nested calls?
Like using one single REST call to get all the tx detail