TRANSFER_TO_ME webhook event
complete
A
Allen Firstenberg
It would be useful to have, in addition to the TRANSFER event, a TRANSFER_TO_ME event. This would be similar to the DONATE event, except that it would be usable by non-creators. (Alternately - the DONATE event could be used, but allowed for non-creators.)
The information included would be the same as for DONATE and TRANSFER, but would always include the "creator approved" data - so the recipient would always be able to determine who has sent the coin.
It is important to note that this would provide no more data than is
already
available in a user's portfolio transactions. It would just provide an automated way to do so.Use cases for this allow for a "Vending machine" (or "Jukebox" or "Arcade game") model, where a person could deposit coin first and then take some action based on how much has been deposited. The advantage of this over an OAuth "initiate transfer" is that it does not need to be initiated through a website or a web interface - it could be initiated from the Rally website or through something like the discord bot.
Russell Spence
complete
Russell Spence
in progress
Internal Ticket: https://starcard.atlassian.net/browse/MXR-379
May make S14, but not sure.
Russell Spence
https://starcard.atlassian.net/browse/MXR-413 has been completed - transaction IDs should be returned now.
The other ticket has been added to S13, but might not completed in that sprint.
Russell Spence
planned
We discussed this issue awhile back, but basically this breaks down into two problems: the ability to track transactions, and the ability to get events that only relate to the specific user.
Transaction Tracking
Internal Ticket: https://starcard.atlassian.net/browse/MXR-413
May not make S11, but it will definitely be released in S12.
User Specific Events
Internal Ticket: https://starcard.atlassian.net/browse/MXR-379
Planned short term 1 - 3 months.
Bret Kinsella
Much of Rally's initial concept appears focused around individual creators as opposed to communities of creators. In the former scenario, having a few centralized features to enable fans and the creator to interact could be sufficient. However, in communities of creators we need more flexibility for participants beyond the creator to have access to certain types of data or at least enable the coin sponsor to authorize access to these features. We can develop much more interesting mechanical coin use cases that drive far higher ongoing utility and transaction volume by enabling certain data permissions and events.