mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 0,2,5: closing transaction not (mutual) close transaction.

Browse Source 
Be consistent.
This commit is contained in:
Hiroki Gondo 2018-11-29 16:17:23 +09:00 committed by Christian Decker
parent 7f68780c20
commit c423308886
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
00-introduction.md
View File

@ -267,7 +267,7 @@ See [BOLT #11: Invoice Protocol for Lightning Payments](11-payment-encoding.md)
* *Unilateral close*:
* An uncooperative close of a *channel*, accomplished by broadcasting a
*commitment transaction*. This transaction is larger (i.e. less
efficient) than a *mutual close transaction*, and the *peer* whose
efficient) than a *closing transaction*, and the *peer* whose
commitment is broadcast cannot access its own outputs for some
previously-negotiated duration.
* _See related: mutual close, revoked transaction close_

4
02-peer-protocol.md
View File

@ -505,7 +505,7 @@ The `shutdown` response requirement implies that the node sends `commitment_sign
Once shutdown is complete and the channel is empty of HTLCs, the final
current commitment transactions will have no HTLCs, and closing fee
negotiation begins. The funder chooses a fee it thinks is fair, and
signs the close transaction with the `scriptpubkey` fields from the
signs the closing transaction with the `scriptpubkey` fields from the
`shutdown` messages (along with its chosen fee) and sends the signature;
the other node then replies similarly, using a fee it thinks is fair. This
exchange continues until both agree on the same fee or when one side fails
@ -532,7 +532,7 @@ The sending node:
transaction, as specified in [BOLT #3](03-transactions.md#closing-transaction).
The receiving node:
- if the `signature` is not valid for either variant of close transaction
- if the `signature` is not valid for either variant of closing transaction
specified in [BOLT #3](03-transactions.md#closing-transaction):
- MUST fail the connection.
- if `fee_satoshis` is equal to its previously sent `fee_satoshis`:

2
05-onchain.md
View File

@ -160,7 +160,7 @@ it to be processed.
# Mutual Close Handling
A mutual close transaction *resolves* the funding transaction output.
A closing transaction *resolves* the funding transaction output.
In the case of a mutual close, a node need not do anything else, as it has
already agreed to the output, which is sent to its specified `scriptpubkey` (see