lightninglabs / lightninglabs/L402
LSAT and liquidity management (noob question)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 91
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
This is a very high-level question to understand how the end-to-end flow fits with lightning (~not really, the real reason is that I wanted to hijack issue number 1~ :smiling_imp: - EDIT: damn I only got number 5, even though I can't see any closed issue).
Let's imagine that an API proposes metered access via LSAT. Users that want access to that API will either need a direct channel or a route where none of the intermediate hops require a base fee, right? Otherwise the cost of the routing fees would very likely exceed the cost of the LSAT.
If we take the option of having a direct channel to the API provider, that channel will likely be quite unidirectional (the user will be making payments, but not the other way around). Once it's depleted on the user's end, the user loses access to the API. That means users need to proactively manage liquidity to make sure they're always able to pay for their LSATs, right?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or implementation entry point. Start by clarifying whether an explanatory answer or documentation change is wanted; it is done only when the LSAT liquidity and routing-fee questions have an agreed, documented resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, payments
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100