⭐ Merited by Welsh (2)
Here I would like a clarification what is exactly not possible. Can't the payer initiate a Lightning transaction, waiting a time (e.g. 24 hours) until the other node pops up to sign its part? It's clear that both have to be online at the same time somewhen, at least for a moment. And: Does the "watching" node need to be connected with the destination node?
One of the problems is that even if the other party would come back online for a few seconds after 24 hours, the route might have changed so the transaction would not take place. The word "watching" was probably the worst one that I could have used. I was thinking of a service which would accept payments on behalf of someone (connection to both nodes would have to exist) and then send it to the destination node on demand.
Here an interesting addition is if there is a "standard" timeout/lock time for the Lightning "penalty transaction" - to know how often you should be online to avoid being cheated. I've currently no Lightning node running (I tested Eclair some weeks ago but it's now outdated, so I can't answer that question myself.) Normally, you should be able to set the timeout you want, but what are the chances you will find a route or a partner to open a channel with?
I'm quite sure that locktime is being negotiated while you are trying to open a channel therefore it will vary for your each connection with the other node. Finding someone with the same channel policy might be a bit difficult.
It's one year since BCH fork, and after all that debate here's the conclusion 
.
I quite disagree with it. Block weight should stay 1 MB forever. Makes no sense to me increasing it.
.I quite disagree with it. Block weight should stay 1 MB forever. Makes no sense to me increasing it.
I didn't write that we have to increase the block weight 30 times. There are plenty of things that can be done in the future before increasing the block weight, for example, implementing channel factories which allow users to create new Lightning Network channels from existing ones - no need to broadcast closing and opening transaction. I have changed the sentence you quoted in order to make it more neutral
