I implemented memos on the recurrent transfers, so it would be possible for front ends to add some identifier on recurrent transfers and build on it :)
In terms of apis I haven't built many apis yet. So far it's just an api call "find_recurrent_transfers" to see where your recurrent transfers are going. Thinking of building more in hivemind or directly in hived.
I think this is needed also the other way around. To see which recurring transfers an account is going to receive. Suppose you are a content creator you want to see the 'incoming' recurring transfer, not the outgoing.
If you can include all the operation details (including the memo) will be great :)
Another point is how to fetch the transfers history. Are you going to use a new operation type? Or just a standard transfer? Ideally we would like to show a filterable list of all the recurring transfer received/sent by an account.
Everything else in my opinion should not be included in the core API 👍
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.
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).
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 👍