Create interface to allow for (optional?) manual handling of liqudity requests

[tnull]

Our current initial interface for the liqudity services was kept very barebones on purpose.

For a more production-ready deployment of these services, we should add an interface that would allow the user to customize all the core parameters on a per-request basis (e.g., token, limits, fees, etc).

We could consider making this the main interface that always needs to be implemented, or, could introduce a manually_handle_liquidity_requests flag that would allow users to sidestep the default behavior.

[tosynthegeek]

Can I take this? @tnull

[tnull]

Can I take this? @tnull

Ah, thanks for the interest, but I think there is still some ongoing discussion around this, and I believe @aylagreystone also considered implementing this. If not, I might end up doing it myself as there is a bunch of additional context required that should be considered as part of this task.

[tosynthegeek]

Can I take this? @tnull

Ah, thanks for the interest, but I think there is still some ongoing discussion around this, and I believe @aylagreystone also considered implementing this. If not, I might end up doing it myself as there is a bunch of additional context required that should be considered as part of this task.

Got it. Would look inot another issue

[tnull]

Got it. Would look inot another issue

Cool. Also feel free to ping me on LDK Discord so we can discuss open issues. Recently a lot of issues have already been picked up by new contributors, so might be easier to discuss what's left first.

[tosynthegeek]

Cool. Also feel free to ping me on LDK Discord so we can discuss open issues. Recently a lot of issues have already been picked up by new contributors, so might be easier to discuss what's left first.

Sure pinging you now..