mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-22 08:08:11 +00:00
Edited ch14_applications.adoc with Atlas code editor
This commit is contained in:
parent
5e2cdf38e5
commit
c8ff99ad73
@ -551,7 +551,7 @@ image::images/mbc3_1403.png["Emma's payment channel with Fabian, showing the com
|
||||
|
||||
==== Making Trustless Channels
|
||||
|
||||
The channel we just described works, but only if both
|
||||
The channel ((("payment channels", "trustless channels", id="payment-channel-trustless")))((("trustless channels", id="trustless-channel")))((("timelocks", "trustless channels", id="timelock-trustless")))we just described works, but only if both
|
||||
parties cooperate, without any failures or attempts to cheat. Let's look
|
||||
at some of the scenarios that break this channel and see what is needed
|
||||
to fix those:
|
||||
@ -693,7 +693,7 @@ settlement transaction they can close the channel and redeem their
|
||||
balance immediately. Worst case, one of the parties can be petty, refuse
|
||||
to cooperate, and force the other party to do a unilateral close with
|
||||
the most recent commitment transaction. But if they do that, they have
|
||||
to wait for their funds too.
|
||||
to wait for their funds ((("payment channels", "trustless channels", startref="payment-channel-trustless")))((("trustless channels", startref="trustless-channel")))((("timelocks", "trustless channels", startref="timelock-trustless")))too.
|
||||
|
||||
==== Asymmetric Revocable Commitments
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user