You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
partner is a PC (e.g. by checking it has Delivery capability); OR
partner is the closing side
The first point is because PC always try to auto-settle early; the 2nd will have LCs agreeing on giving priority to the closing side to settle, since usually they're the ones most/first interested in getting their funds back. The delaying side could still try to auto-settle in e.g. revealTimeout blocks after, if the channel wasn't settled by then.
When closing a channel and reaching the end of the settlement window, both channel partners will send a settlement transaction to the blockchain.
As those coincide, only one will go through, while one will be rejected. This could be observed while running the BF1 scenario.
To limit failing transaction we could offset the transactions ending by the partner with the higher address by a number of blocks.
The text was updated successfully, but these errors were encountered: