Skip to content

Commit 52f0f8d

Browse files
Leo Weesegitbook-bot
Leo Weese
authored andcommitted
GITBOOK-490: change request with no subject merged in GitBook
1 parent 398fc0d commit 52f0f8d

File tree

2 files changed

+8
-7
lines changed

2 files changed

+8
-7
lines changed

lightning-network-tools/taproot-assets/rfq.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: >-
88

99
When sending Taproot Assets over the Lightning Network, an Edge Node is needed. This Edge Node receives the Taproot Asset in the channel with the direct user and swaps it for bitcoin. As the swap rate between Taproot Assets and bitcoin likely fluctuates, the user may make a Request for Quote to the Edge Node before generating a Lightning Network invoice or initiating a payment.
1010

11-
This request is made using [BOLT 01](https://github.com/lightning/bolts/blob/master/01-messaging.md) messages over an existing encrypted and authenticated [BOLT 08](https://github.com/lightning/bolts/blob/master/08-transport.md) connection. The connection already exists because it is used for establishing and coordinating the Taproot Asset Channel in a way very similiar to normal Lightning channels. For more information about connection and messaging, see the [Last Mile Routing](https://github.com/Roasbeef/blips/blob/tap-blip/blip-tap.md#last-mile-routing) section of [Taproot Asset Channels bLIP](https://github.com/Roasbeef/blips/blob/tap-blip/blip-tap.md).
11+
This request is made using [BOLT 01](https://github.com/lightning/bolts/blob/master/01-messaging.md) messages over an existing encrypted and authenticated [BOLT 08](https://github.com/lightning/bolts/blob/master/08-transport.md) connection. The connection already exists because it is used for establishing and coordinating the Taproot Asset Channel in a way very similar to normal Lightning channels. For more information about connection and messaging, see the [Last Mile Routing](https://github.com/Roasbeef/blips/blob/tap-blip/blip-tap.md#last-mile-routing) section of [Taproot Asset Channels BLIP](https://github.com/Roasbeef/blips/blob/tap-blip/blip-tap.md).
1212

1313
[Learn more: Edge Nodes](../../the-lightning-network/taproot-assets/edge-nodes.md)
1414

the-lightning-network/taproot-assets/edge-nodes.md

+7-6
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,17 @@ description: >-
66

77
# Edge Nodes
88

9-
Taproot Assets can be deposited into Lightning Network channels. Such Taproot Asset channels are not announced to the network, but are available as “private” channels to both channel partners.
9+
Taproot Assets can be deposited into Lightning Network channels. These Taproot Asset channels are not announced to the network, but are available as “private” channels to both channel partners.
1010

11-
Typically, these unannounced channels are between a client (the wallet of an end-user, running on a mobile device or personal computer) and a service provider (a routing node operating on a server). The service provider is always available and well connected to the larger network through public channels, while the client only comes only sporadically to make or receive a payment.
11+
Typically, unannounced channels are between a client (the wallet of an end-user, running on a mobile device or personal computer) and a routing node operating on a server. The routing node is always available and well connected to the larger network through public channels, while the client comes only sporadically online to make or receive a payment.
1212

13-
In the context of Taproot Assets, an Edge node is a service provider with multiple public Bitcoin channels to the Lightning Network, and unannounced Taproot Assets channels with their clients. They may have multiple channels per client, for example to facilitate the transfer of multiple asset types.
13+
In the context of Taproot Assets, an Edge node is a specialized routing node with multiple public Bitcoin channels to the Lightning Network, and unannounced Taproot Assets channels with their clients. They may have multiple channels per client, for example to facilitate the transfer of multiple asset types.
1414

1515
What makes an Edge node different to an ordinary routing node or Lightning Service Provider is the ability to swap the Taproot Asset into BTC or vice versa, and route the value of the payment over the greater Lightning Network.
1616

1717
This enables a Taproot Assets-aware Lightning wallet to hold a Taproot Asset, but pay to any Bolt 11/12 Lightning invoice, LNURL or Lightning address. It also allows this wallet to receive Taproot Assets for any payment made by any existing Lightning wallet.
1818

19-
Through Edge Nodes, Taproot Assets-enabled wallets are able to plug into the existing network effects of the Lightning Network, and are able to interact with services and users that are not aware of Taproot Assets.
19+
Through Edge nodes, Taproot Assets-enabled wallets are able to plug into the existing network effects of the Lightning Network, and are able to interact with services and users that are not aware of Taproot Assets.
2020

2121
As Edge nodes swap Taproot Assets to BTC through traditional [HTLCs](../multihop-payments/hash-time-lock-contract-htlc.md), they do not hold client assets or require custodial arrangements of any other kind.
2222

@@ -26,11 +26,12 @@ As Edge nodes swap Taproot Assets to BTC through traditional [HTLCs](../multihop
2626

2727
* **Open channels**
2828

29-
Similar to a Lightning Service Provider, an Edge node might be expected to open Taproot Asset channels to clients on demand. It might charge a fee for this service, or operate under the expectation of generating revenue through future routing activity
29+
Similar to a wallet or professional routing node, an Edge node might be expected to open Taproot Asset channels to clients on demand. It might charge a fee for this service, or operate under the expectation of generating revenue through future routing activity.
3030

3131
* **Quote swap rates**
3232

33-
Before the client performs a swap from Taproot Assets to Bitcoin, it will expect to get a quote from the Edge node. As Lightning invoices are denominated in Bitcoin, this quote is necessary for the client to know how much of their Taproot Assets they are expected to pay: “This invoice is over 10,000 satoshis, how many Taproot-USD will this cost me?”\
33+
Before the client performs a swap from Taproot Assets to Bitcoin, it will expect to get a quote from the Edge node. As Lightning invoices are denominated in Bitcoin, this quote is necessary for the client to know how much of their Taproot Assets they are expected to pay: “This invoice is over 10,000 satoshis, how many Taproot-USD will this cost me?”
34+
3435
Conversely, when generating a Lightning invoice, a quote is necessary for the client to generate the invoice: “I would like to receive 10 Taproot-USD, what amount of satoshis should I make this invoice out to?”\
3536
\
3637
As Bitcoin’s exchange rate is volatile, spreads offered by Edge providers may differ based on how long they are valid for. When paying an invoice quotes only need to be valid for a few seconds, while invoices require quotes for the period of their validity.\

0 commit comments

Comments
 (0)