raises hand We are building a VPN type p2p network that uses LN. It's a very interesting subject because while LN itself is focused on a certain use case, and thus it has a set of design principles that support that use case, but apps built on it will need more functionality, just as LN itself demanded changes to accommodate it on L1.

Apps built with LN as an incentive/security will require small changes in order to function optimally. 0 conf channels, for example, were pioneered by mobile bitcoin wallet LSPs, but there is other things, which other protocols might require, such as my initial, early ideas suggest that supporting very long lived 3 of 3 channel opens greatly improves its payment latency and simplifying path selection, something that really isn't possible on the base L2...