From 2fa325f06fb7762e311a13bdd07c95af0c836ee2 Mon Sep 17 00:00:00 2001 From: "kristen@oreilly.com" Date: Fri, 19 Nov 2021 12:53:12 -0800 Subject: [PATCH] Edited 08_routing_htlcs.asciidoc with Atlas code editor --- 08_routing_htlcs.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/08_routing_htlcs.asciidoc b/08_routing_htlcs.asciidoc index ded1b1e..aa44a7e 100644 --- a/08_routing_htlcs.asciidoc +++ b/08_routing_htlcs.asciidoc @@ -34,7 +34,7 @@ This process of connecting a series of payment channels with end-to-end security In this chapter, we'll dive into the mechanism of routing in the Lightning Network, detailing the precise manner in which payments flow through the network. First, we will clarify the concept of routing and compare it to that of pathfinding, because these are often confused and used interchangeably. Next, we will construct the fairness protocol: an atomic, trustless, multihop protocol used to route payments. To demonstrate how this fairness protocol works, we will be using a physical equivalent of transferring gold coins between four people. Finally, we will look at the atomic, trustless, multihop protocol implementation currently used in the Lightning Network, which is called a hash time-locked contract (HTLC). -=== Routing versus Pathfinding +=== Routing Versus Pathfinding ((("pathfinding","routing versus")))((("routing","pathfinding versus")))It's important to note that we separate the concept of _routing_ from the concept of _pathfinding_. These two concepts are often confused, and the term _routing_ is often used to describe both concepts. Let's remove the ambiguity before we proceed any further.