Superfluid with the concept of streaming money by creating flows among users has opened doors for lot of applications and use cases. But, streams on superfluid are constant flow agreements, which can't be changed once the streams is started. This restricts the use cases and flexibility for the end users. We are trying to build a more customized version of the protocol which will be powered by the middleware contracts between 2 users.
The solution is to build a checkpoint based middleware giving an extra ability on top of the existing streams. While creating a stream, the sender can configure the checkpoint, which can be mutually decided among the parties (sender and receiver). Doing that, the contract will ensure that the receiver of the stream submits a proof (not explicitly to the contract). On every checkpoint, the proof till date will be verified and modifications to the stream will be made accordingly. The contract adjusts the flow accordingly. If the middleware is abstracted, then it gives a functionality to pause the stream whenever the proof is not submitted and resume when the proof is submitted. The sender can visualize the work done on each checkpoint and can claim the remaining funds which are locked in the contract (future work).
Contractual payments or payments for any verifiable proof based work.
Technologies used
Discussion