Log in to customize your experience and get involved.
I am going to write a longer post about this question soon as part of our final report on the research on options for better integration of (micro)payments with Coil/WM/ILP (with a focus of the context of our project).
Automated micropayments could work well with Coil/WM out of the box. Probably directly via the Coil API, although that would make it wallet dependent again.
My personal favourite, and for which Coil or generally crypto-based solutions are potentially a great fit, is the staking-based access. This way you can cryptographically verify that the stake/deposit has been made and that can't be withdrawn. Though I think that Coil does not support such a use case yet.
I didn't find conclusive answers if Coil could be used for ongoing subscriptions, as it does not seem to support that (yet) either. Maybe I am mistaken and haven't found the right docs. Do you know where I could read up on both of those cases?
Other unanswered questions I have, and you may be the right person to ask or help me find another person to ask, is how multi-recipient transactions could/would work with ILP and WM?
This would be necessary for example to implement use cases like platform fees (e.g. 10% of the creator revenue), or pay multiple contributor in a collection directly, instead of creating a platform dependent proprietary fund distribution mechanism.
These questions are not immediately necessary to answer in order to fullfill our current grant requirements, but they are for a subsequent proposal on extending the WM/coil integrations and to offer a wider range of monetization methods (auto-payment, subscriptions, staking-based access)
Thanks for the help!
we have now found the cause of our challenges, and they were burried in a misunderstanding on how the WebMonetization implementation currently works. It became clear now that the WebMonatization currently only supports a stream of payments for as long as the user is active on a page, or decided to start/stop the payment stream.
Given this I have to revisit some of my analysis on where things can be used:
Would be great to know where WM has challenges to be implementing those features so the community can think/work along.
We’d love for you to be a part of this community.