mirror of
https://github.com/lightning/bolts.git
synced 2025-01-18 21:32:31 +01:00
Fixes to existing spec
This commit is contained in:
parent
9e8e29af9b
commit
bfc66e5e4a
@ -397,8 +397,7 @@ committed HTLCs:
|
||||
in [Commitment Transaction](#commitment-transaction).
|
||||
1. Calculate which committed HTLCs need to be trimmed (see [Trimmed Outputs](#trimmed-outputs)).
|
||||
2. Calculate the base [commitment transaction fee](#fee-calculation).
|
||||
3. Subtract this base fee from the funder (either `to_local` or `to_remote`),
|
||||
with a floor of 0 (see [Fee Payment](#fee-payment)).
|
||||
3. Subtract this base fee from the funder (either `to_local` or `to_remote`).
|
||||
3. For every offered HTLC, if it is not trimmed, add an
|
||||
[offered HTLC output](#offered-htlc-outputs).
|
||||
4. For every received HTLC, if it is not trimmed, add an
|
||||
@ -451,6 +450,7 @@ These pubkeys are simply generated by addition from their base points:
|
||||
pubkey = basepoint + SHA256(per_commitment_point || basepoint) * G
|
||||
|
||||
The `localpubkey` uses the local node's `payment_basepoint`;
|
||||
The `remotepubkey` uses the remote node's `payment_basepoint`;
|
||||
the `local_htlcpubkey` uses the local node's `htlc_basepoint`;
|
||||
the `remote_htlcpubkey` uses the remote node's `htlc_basepoint`;
|
||||
the `local_delayedpubkey` uses the local node's `delayed_payment_basepoint`;
|
||||
|
Loading…
Reference in New Issue
Block a user