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
It would be great if CLBOSS could offer config options to optimize a node specifically for receiving payments. Consider a scenario where a business is focused primarily on receiving payments for its services and does not engage much in spending.
Currently, I am developing a user interface for CLBOSS, with the goal of simplifying configuration that is tailored to three different user types:
Alice: Primarily sends payments.
Bob: Sends and receives payments equally.
Dave: Primarily receives payments.
My vision is to present these configuration options in a user-friendly manner, abstracting the technical details. Users like Dave, who simply want to optimize for receiving payments, should be able to select a straightforward option, such as "I mostly want to receive payments." Clams will then pass configuration options to CLBOSS to prioritize inbound liquidity.
I will leave the technical details open for discussion, but the ultimate goal is to optimize a node for receiving payments.
Cheers!
The text was updated successfully, but these errors were encountered:
It would be great if CLBOSS could offer config options to optimize a node specifically for receiving payments. Consider a scenario where a business is focused primarily on receiving payments for its services and does not engage much in spending.
Currently, I am developing a user interface for CLBOSS, with the goal of simplifying configuration that is tailored to three different user types:
My vision is to present these configuration options in a user-friendly manner, abstracting the technical details. Users like Dave, who simply want to optimize for receiving payments, should be able to select a straightforward option, such as "I mostly want to receive payments." Clams will then pass configuration options to CLBOSS to prioritize inbound liquidity.
I will leave the technical details open for discussion, but the ultimate goal is to optimize a node for receiving payments.
Cheers!
The text was updated successfully, but these errors were encountered: