Quote from: wpwrak on December 30, 2017, 06:50:54 PM

Quote from: HeRetiK on December 30, 2017, 05:14:01 PM

Maybe I misunderstand you, but what you describe sounds pretty close to what SegWit is already doing:

https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki

Hmm, I'm still struggling to understand what SegWit exactly is :-) The BIP touches a lot of issues and suggests many future developments, so I'm not sure how much of what SegWit is intended to do is actually implemented.

One explanation I found basically describes it as an accounting trick: you move part of the data in the block to a different place and declare bytes there to be smaller than bytes elsewhere, which allows you to grow blocks a little without exceeding the 1 MB limit. But, if I understand this right, the transactions would still be part of the same block.

If SegWit allows most of the transaction data to travel through a different channel, then it would be indeed what I've been looking for.

Thanks !

- Werner

I think it mostly is because the efficiency. Your approach still need to download the actual transaction data during the verification phase. LN does not need to put and verify every small transactions on the main blockchain hence it's more scalable and efficient.