I think this is needed also the other way around
Haha I figured you'd say that. There is a good chance that we might implement this at the hivemind level instead of hived because those kind of indexes increase the ram requirements of nodes and we want to avoid that.
Another point is how to fetch the transfers history
New virtual operation ! Two actually, you will find them in the usual get account history call
fill_recurrent_transfer_operation and failed_recurrent_transfer_operation
fill is pushed when the recurrent transfer was a success, failed is when it wasn't (if the user ran out of money).
Ideally we would like to show a filterable list of all the recurring transfer received/sent by an account.
I assume that that shouldn't be a problem with your current implementation of the wallet like where you sort by "outgoing/incoming"
Awesome, thanks 👍