|
|
|
|
|
by jlrubin
3019 days ago
|
|
Actually, as a quirk of the design, the final transaction MUST be a series of transactions which are 'conflict free'. For instance, if the close gives Alice 10 lumens and Bob 10 lumens, these must be expressed as two transactions. Otherwise, if Bob deletes his account, this causes a conflict when the transaction is published (and the transaction will fail). If they are two separate transactions, there is no problem if Bob deletes his account. |
|
> if the close gives Alice 10 lumens and Bob 10 lumens, these must be expressed as two transactions.
As in, in this case, closing requires two transactions, Escrow -> Alice and Escrow -> Bob?
Can closing allow for more than n transactions, where n is the number of participants in the channel?