1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-22 16:18:11 +00:00

Edited ch14_applications.adoc with Atlas code editor

This commit is contained in:
clenser 2023-10-19 18:23:17 +00:00
parent 7b69880144
commit e76f104e50

View File

@ -697,7 +697,7 @@ to wait for their funds ((("payment channels", "trustless channels", startref="p
==== Asymmetric Revocable Commitments ==== Asymmetric Revocable Commitments
Another way to handle the prior commitment states Another way((("payment channels", "asymmetric revocable commitments", id="payment-channel-revoke")))((("asymmetric revocable commitments", id="asymmetric-revoke-commit")))((("commitment transactions", "asymmetric revocable commitments", id="commit-revoke")))((("revocable commitments", id="revoke-commit"))) to handle the prior commitment states
is to explicitly revoke them. However, this is not easy to achieve. A is to explicitly revoke them. However, this is not easy to achieve. A
key characteristic of Bitcoin is that once a transaction is valid, it key characteristic of Bitcoin is that once a transaction is valid, it
remains valid and does not expire. The only way to cancel a transaction remains valid and does not expire. The only way to cancel a transaction
@ -911,7 +911,7 @@ innovation in this technology. With this construct, the channel can
remain open indefinitely and can have billions of intermediate remain open indefinitely and can have billions of intermediate
commitment transactions. In implementations of Lightning commitment transactions. In implementations of Lightning
Network, the commitment state is identified by a 48-bit index, allowing Network, the commitment state is identified by a 48-bit index, allowing
more than 281 trillion (2.8 × 10^14^) state transitions in any single more than 281 trillion (2.8 × 10^14^) state transitions in ((("payment channels", "asymmetric revocable commitments", startref="payment-channel-revoke")))((("asymmetric revocable commitments", startref="asymmetric-revoke-commit")))((("commitment transactions", "asymmetric revocable commitments", startref="commit-revoke")))((("revocable commitments", startref="revoke-commit")))any single
channel. channel.
==== Hash Time Lock Contracts (HTLC) ==== Hash Time Lock Contracts (HTLC)