Laundry list of inter-peer wire protocol changes

The discussion is about reserving before locking and its optimization to reduce the risk of locking funds in payment channels. If the remaining part of the route does not exist, it can cause undoing the locking which increases latency. The bi-directional nature of the channel is realized with decreasing lock times. It is necessary for bi-directional routing. Meeting points can be bypassed if beacons are less connected. The “reserving” stage allows you to set a tighter value on the HTLC time-outs. If onioning is used, source routing is needed. There can be many intermediate nodes between payer and payee, and between meeting point and payee. A more interactive protocol can be implemented that would fit fairly nicely.