Single-asset LN channel design considerations #25
Labels
[Bifrost]
LNP protocol extensions enabling RGB, DEX, storage etc
help wanted
Extra attention is needed
question
Further information is requested
[RGB]
Specs related to client-validated state management system
Projects
Milestone
On RGBCon0 in Milano @renepickhardt proposed to use single-asset LN channels, which:
Nevertheless, using single-asset LN channels for RGB has its own trade-offs: addition of each asset will require new channel funding transaction, which limits scalability. Here I'd like to discuss the ways how we can mitigate this issue.
Channel splitting
Use channel splitting: create a new transaction spending funding output, which will contain new version of funding outputs, one per asset. Don't publish this information on-chain.
Pros:
Cons:
Channel factories
Use channel factories: the same of above, but instead of splitting within the existing channel we use channel factory to create a new channel. The pros and cons are exactly like the above
Channel virtualization
Channel "superposition"/virtualization within the same commitment transaction: nodes operate multiple channels sharing single commitment transaction.
Cons:
Pros:
The text was updated successfully, but these errors were encountered: