We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Instead of calling all invoices, txs, and payments at once on the Activity view, we should use the index_offset parameters to do paging.
Activity
index_offset
https://lightning.engineering/api-docs/api/lnd/lightning/list-payments/ https://lightning.engineering/api-docs/api/lnd/lightning/list-invoices/ https://lightning.engineering/api-docs/api/lnd/lightning/get-transactions/
The biggest challenge is putting the data together. Ideally LND would have a single Activity endpoint we could use
We could potentially be able to do something similar for CLNRest using the custom SQL calls.
Related issues: #2465 #2390
The text was updated successfully, but these errors were encountered:
shubhamkmr04
No branches or pull requests
Instead of calling all invoices, txs, and payments at once on the
Activity
view, we should use theindex_offset
parameters to do paging.https://lightning.engineering/api-docs/api/lnd/lightning/list-payments/
https://lightning.engineering/api-docs/api/lnd/lightning/list-invoices/
https://lightning.engineering/api-docs/api/lnd/lightning/get-transactions/
The biggest challenge is putting the data together. Ideally LND would have a single Activity endpoint we could use
We could potentially be able to do something similar for CLNRest using the custom SQL calls.
Related issues:
#2465
#2390
The text was updated successfully, but these errors were encountered: