feat: adding payment stream creation event to indexer #213
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
links234
reviewed
Oct 1, 2024
ffarall
requested changes
Oct 3, 2024
ffarall
requested changes
Oct 4, 2024
undercover-cactus
force-pushed
the
feat/payment-streams
branch
from
fdbc74b to
dc80e12
Compare
…not left as 0 when user is without funds
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.
This PR add the logic to have the indexer processing the payment stream creation events.
We are adding a new table
PaymentStreamthat aggregate the payment stream created (with fixed rate and dynamic rate). The table has an extra columntotal_amountthat keep record of the total amount paid to the provider (not yet implemented).