The idea behind using LNSymmetry is to then have multi-party channels.
Yes, that's a more advanced version of the idea. But multi-party channels have their own problems, in particular, coordination. It's very difficult to get more than a few parties coordinated.
Which again, has limited enthusiasm for Eltoo.
The first thought that would come to mind is like a mempool for multi-party channels.
So for example we have this transaction batching service https://peachbitcoin.com/blog/group-hug/
So you would just modify that to return a multi-party channel rather than outputs to all these different addresses.
Now that doesn't work if the architecture incentivizes using nodeIDs as pseudonyms. So in that case they might coordinate on amboss.space or maybe they would coordinate over here; https://lightningnetwork.plus/ because these style of channel opens already look very similar to the coordination you need for channel factories.
Maybe channel factories work a bit like a video game guild where you send a message requesting to join and the participants of the channel factory do something similar to a channel splice to get you added in
Still though, I'm gonna go reread some whitepapers specifically how they handle the uncoorperative close mechanism.
reply
I really like https://lightningnetwork.plus/ and have used it to bootstrap liquidity for one of my nodes. Folks should take a look if they have not seen it.
I look forward to when we can use such a pseudo social-network for channel factories and multi-party channel coordination.
reply