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

Decide on Information to Persist in barq's Database #7

Open
tareknaser opened this issue Jun 27, 2024 · 2 comments
Open

Decide on Information to Persist in barq's Database #7

tareknaser opened this issue Jun 27, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@tareknaser
Copy link
Collaborator

We need to decide what information barq should persist on disk in its database. This should include details about past payments and potentially network data to help route payments more efficiently. Additionally, the database should store logs of past payments.

We also need to consider how to collect this information from Core Lightning in barq-plugin, including which RPC commands to call.

@raehat
Copy link
Collaborator

raehat commented Jul 4, 2024

@tareknaser I am considering storing data for all payments made with Barq in a NoSQL format, such as a JSON file. The usage of this data can be determined when writing a strategy. Let me know if I should move ahead with this approach.

@tareknaser
Copy link
Collaborator Author

For this issue, the initial step is to determine what information would be useful to persist. The method of persisting this information is out of scope for now. What I had in mind is just:clear and structured answers to the following questions:

  • What information about past payments should be stored?
  • What information about the network should be stored to improve payment routing?

@raehat raehat added documentation Improvements or additions to documentation enhancement New feature or request and removed documentation Improvements or additions to documentation labels Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants