Recurring payments: an idea for maintaining services in Kusama.
We'd like to revisit the idea of Recurring Payments.
This idea is basically a call that sets up in motion repeating payments following certain conditions. It would keep funding it from the treasury until there was a motion to cancel it or until the treasury runs out of funds. The logic will be similar to a vesting function.
This could potentially be used on social contract designs for maintaining services on Kusama, to maintain the contract onchain after offchain discussion on agreement conditions. The call should be approved and cancel by the council, only to be submitted by a motion.
We'd like to open the discussion here for the community to add to the original idea. After, we will move on to the implementation of the call, if the community agrees.
Comments (6)
Already possible via Democracy+Scheduler :) Personally I think that it makes sense to restrict long-term scheduled payments like this to democracy
As far as I could understand by my discussion with Gav and Shawn, Scheduler is not designed to handle any number of objects to be scheduled, but its meant for system level scheduling that would be hard to do in any other way. If eventually we used the Scheduler for more a large number of outstanding payments, we would be pushing it past what it was designed for. Shawn explained that in general for these kind of systems we want the user to trigger payment so they pay some fee and Kusama's weight system can handle the load balancing.