You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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.
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?
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.The text was updated successfully, but these errors were encountered: