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