Implement proof of concept of Eltoo #1267
Labels
C. Payment Channel
Related to Flash TestNet
difficulty-hard
An issue which requires a lot of research, or requires a lot of modification to the codebase
Story-Points:13
This takes > 7 days to complete
type-feature
An addition to the system introducing new functionalities
Milestone
As mentioned in #1266, there are currently two main competitive LN update mechanisms. LN-Penalty, and Eltoo. LN-Penalty has three compatible implementations, whereas Eltoo is still blocked from being developed & deployed on Bitcoin due to a requirement for a new sighash type (BIP 118).
LN developers seem to be in agreement that Eltoo is a great evolution over LN-Penalty, and may end up replacing the penalty update protocol. Note that both protocols can be used at the same time on Bitcoin.
In our case we have a big advantage over Bitcoin. We can develop the protocol without being blocked by the requirement of doing a soft-fork. In addition to that our PoS system could potentially make it easy to create multi-party channels - we could even make this multi-party channel creation be part of the protocol rules (think quorum shuffling, for example).
As a first step we can try to implement a proof of concept of Eltoo. There are many moving parts, and we should aim to have the simplest proof of concept.
This will probably require the following:
Thereafter it should be fairly simple to implement multi-party channels as well.
The text was updated successfully, but these errors were encountered: