📅 Original date posted:2017-01-16 📝 Original message: Rusty,I'm on the side that has given nothing to the code but is following with a lot of attention the evolution of LN and Segwit.We are ready to help.  What can be done in your opinion? Stefano Pepe CEO, UniquID Inc. uniquid.com On Sun, Jan 15, 2017 at 6:39 PM -0800, "Rusty Russell" <rusty at rustcorp.com.au> wrote: "Andrés G. Aragoneses " writes: > Hi there, > > Seems like the list is a bit dormant these days. Yes, most of the activity has been on the github repository: github.com/lightningnetwork/lightning-rfc > Is it because of the low chances of SegWit activation given that it stalled > at ~26%? > > On this topic, I would like to ask about the feasibility of LN without > SegWit, given these circumstances. > > Some has been said in the past, I've been reading through the archives. But > in them, everybody seemed overly enthusiastic about the activation of > SegWit (maybe given that OP_CLTV and OP_CSV activated without hassle). If segwit doesn't activate, something is badly broken in Bitcoin. This is not really a lightning issue; there's been no significant technical objection to segwit, and it really does make Bitcoin work better. I'm glad that miners are cautious with their upgrades, and segwit adoption will take time to roll out across products anyway. Let's look again in 6 months. > Which one is more accurate? Is the security problems only related to having > to watch the blockchain? If yes, why cannot one outsource this job to a > server (e.g. the hypothetical server of your light-wallet) in level2? Yes, the problem is outsourcing. You can't hand the outsourcer a penalty transaction signature if you don't know what the bad transaction will look like. And if the signatures are part of the transaction ID, you don't. Hope that helps, Rusty. _______________________________________________ Lightning-dev mailing list Lightning-dev at lists.linuxfoundation.org lists.linuxfoundation.org/mailman/listinfo/lightning-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20170116/49354ae5/attachment.html>