The thing is, we do not want to become dependent on third party services and have to rely on them to do transactions. Services like Xapo is also
centralized and can be shutdown or targeted by hackers and if we rely on these services and they go down, then we are stuffed. So NO, we have
to sort out the scaling problems and this must be done soon.
now imagine your funds are locked into a LN channel with Xapo..
they got shut down.
you broadcast your 'initial channel setup' transaction. (losing xapo income)
so the Xapo administrators broadcast their CSV revoke to claw back the funds and then make you have to be part of the same bankruptcy administration process.
hope this makes you see that LN may not be the end solution either
imagine we are at $1 tx fee due to blockstreams tearing apart of the fee control mechanisms, then offer 75% discount if their 2merkle soft cludge gets activated. people move their funds over to segwit keys hoping for a 75% discount.
46million outputs hit the mempool over months-year to get everyone into new keytypes) bringing the native tx costs up to $4 and resulting in the segwit tx cost getting to $1 (check how fast we went from $0.25-$1 in the last year to show how easy it is to do)
...all for a 'hope' of 2mb utility out of the 4mb buffer(2merkle:block inside a block)
people then complain the mempool is still bloated and tx's are delayed. so now demand that its now made 'hard' by removing the soft 2merkle cludge to make it a real 4mb 1merkle (single block).
the 'fee discount' is removed and now the fee become over $4 to use..
this second scenario is what dvs want to play out first to then hope people prssure themselves into using LN but i thought id make it clear that LN is not an end solution first just to get people to realise the problem/trap they are setting themselves by the whole
'go soft, then LN then hard' roadmap
