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

accounting: time-based balance snapshots #44

Open
Roasbeef opened this issue May 29, 2020 · 1 comment
Open

accounting: time-based balance snapshots #44

Roasbeef opened this issue May 29, 2020 · 1 comment
Labels
enhancement New feature or request feature request Requests for new features

Comments

@Roasbeef
Copy link
Member

During the recent call with several lnd users, the notion of being able to obtain a balance "snapshot" at any period of time came up. I think the use case here is going back and looking at the historical flow of funds within a channel.

FWIW, this is already available in lnd as is, since we store the entire "revocation" chain. However this isn't indexed by "time" and instead uses an auto-incrementing sequence number of each new channel state. The only notion of time for the revocation chain is the absolute expiation heights on any HTLCs possibly present on the commitment transaction.

Alternatively, this can be done by polling lnd periodically, or having faraday use the streaming balance RPCs to update its own local state.

@Roasbeef Roasbeef added enhancement New feature or request feature request Requests for new features labels May 29, 2020
@philipglazman
Copy link

+1 on time-based balance snapshots.

Related feature that would be useful is time-based balance snapshots for each Bitcoin address (on-chain wallet and channel funding txn outputs). I'm not sure how this fits into the Harmony Reporting Standard, so might be a different report entirely.

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

No branches or pull requests

2 participants