eth_listTransactions

[tymat]

This feature has been discussed on gitter in the past and we would like to see this get implemented for accounts and contracts.

Proposal

eth_listTransactions

Returns a list of transaction hashes for a given external or contract account

Parameters

String - the account or contract address

params: [
  "0x385acafdb80b71ae001f1dbd0d65e62ec2fff055"
]

Returns

DATA - A list of transaction hashes

[gavofyork]

This is useless - transactions are merely one way of two ways to send a message to an object ("contract") in Ethereum; CALL would be the other way.

Use logs. It's what they were designed for.

[gavofyork]

would close.

[Gustav-Simonsson]

@gavofyork It's far from useless. For example, it would be very useful for keeping track of non-contract txs, which cannot use logs.

This feature has been requested from several people. We shouldn't force users to only use the platform in a certain way, and If users desire a API call which doesn't conflict with anything or have any significant drawbacks, we should consider adding it.

I'm in favour of adding this.

[obscuren]

So am I. But let the community decide on this. Get enough +1 and it will eventually be considered/added.

[ethernomad]

Maybe messages to non-contract addresses should automatically get a blank log entry? It would store the originating transaction id.

[frozeman]

👍 I fully agree with gustav here. Even though most of the cool stuff can happen in contracts, being able to simply send money from one account to the other will be heavily used. And then you need a easy way to display its transactions (e.g. the wallet needs that for example :) )

I would add a second parameter, which is the nonce, from which on you want to get transactions. This way you don't need to request the whole list over and over again.

[tymat]

eth_listTransactions is very much needed for Ether to Ether transactions. For wallet devs we need a way to present this information to users so they know how their Ether was spent and when it was spent and which TX hashes they occurred in. Adding a separate persistence layer to store this data for easy access is cumbersome and would have to be constantly updated on the client side.

This is very useful and much needed.

[slothbag]

+1 I found myself looking for this feature.. would be great to get it included.

[VoR0220]

👍

[VoR0220]

this is much more efficient IMO than the logs...and there's a lot of use cases for this feature for execution in other contracts.

[VoR0220]

I would add a third optional parameter for number of transactions from the top or bottom (perhaps something python-esque?)

[frozeman]

Though i +1 this feature @VoR0220 you can't get logs only from transactions, as there can also be logs created when one contract interacts with another.. So only relying on this feature won't work.

I don't like the third parameter actually, as a nonce (from which nonce to get tx on), is more than enough to control the tx flow.

[VoR0220]

how does nonce control how many transactions you would like to see?

[d11e9]

👍