Payment Stream module #291
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codegnosis
force-pushed
the
payment_stream_module
branch
from
a59eb8b
to
8726820
Compare
Codegnosis
force-pushed
the
payment_stream_module
branch
from
39b7969
to
744ef23
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The stream module allows the creation of payment streams between senders and receivers as an alternative to traditional subscriptions which can be difficult to implement on a blockchain.
Streams are based on flow rates, which are calculated at coins per second. Owed payments can be claimed at any time by a receiver, and will be sent to the designated receiver wallet at the specified flow rate. For example, if
nnseconds have passed, then (nn * flow_rate) coins will be sent to the receiver wallet.Stream creators (senders) can update the flow rate at any time, which will result in owed coins first being calculated at the old flow rate and sent to the receiver before the new flow rate is implemented for future payments.
Senders may also top up their stream deposits, and cancel a stream at any time. Cancelling a stream results in any outstanding owed payments being sent to the receiver, and the remaining deposits (if any) refunded to the sender.
Additionally, the module supports a Validator Bonus parameter. If set to a positive value, the specified percentage of each payment will be sent to the
feeCollectorfor distribution among the Validators.