Skip to content

Commit edb522f

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

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Typically, unannounced channels are between a client (the wallet of an end-user,
1212

1313
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

15-
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.
15+
What makes an Edge node different to an ordinary routing node 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

0 commit comments

Comments
 (0)