Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

filter by maxiumum [and minimum] payment size and sum [small] payments over different payment size ranges #1329

Open
AndySchroder opened this issue Feb 16, 2023 · 3 comments
Labels
Feature request New feature request

Comments

@AndySchroder
Copy link

Describe the feature

With Distributed Charge (http://andyschroder.com/DistributedCharge/) there are many small payments made as long as power to your building is on or your car is charging. There can be thousands of payments over the course of a month. With Zeus, we now (#1100) have the ability to filter transactions by a minimum size (which can be used to hide all of these small transactions), but it would also be nice to filter by maximum size (to show the small payments only).

Taking it one step further, it would be nice to also be able to aggregate payments within the filtered size range and then sum them based on a common memo and/or destination node public key, and then report sums for different intervals (such as hour, month, day, and year).

These summed intervals could then be optionally displayed along with "normal" transactions. Then, pressing on the summed payments would show the individual payments within the interval.

Related: #83 suggests filtering by memo, but doesn't mention aggregating the small payments over an interval.

I can imagine that there are many other applications where this same feature would be very useful, for example, "Podcasting 2.0", video streaming, audio streaming, VPN services such as https://lnvpn.net/, etc..

@AndySchroder
Copy link
Author

lightningnetwork/lnd#7626 might help make this request more feasible?

@AndySchroder
Copy link
Author

Would like to add a bounty of 50,000 sat for fixing this issue.

@myxmaster
Copy link
Contributor

The thing is, with lots of payments, the retrieval of the complete data set (all payments) can take a long time (and creates high server load for the backend), which is why we need pagination. So we need to think about how to integrate that feature in the UI. Users should understand that it can take a while to create that kind of reports -> it should not look like just another filter/default feature on Activity screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request New feature request
Projects
None yet
Development

No branches or pull requests

2 participants