> For the complete documentation index, see [llms.txt](https://docs.sequentia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sequentia.io/white-paper/4.-asset-tokenization/4.3.-lightning-network-payments.md). # 4.3. Lightning Network payments Lightning network is enabled for all fungible RAS tokens. Sequentia’s Lightning Network wallet functionalities use the same BOLT specifications meant for Bitcoin. It is possible to make an on-chain transaction by opening a payment channel in a token issued on Sequentia, and then all the following payments in that token can be made through that channel. Indeed, the channel can also be used as a route for the payments of other users, even in different tokens. Lightning Network payments are expected to be used on Sequentia, particularly with stablecoin transactions, since they have high liquidity and are frequently transferred between custodial services/exchanges with better means of creating well-balanced channels than the average users. However, in the future, even tokens with lower liquidity might take advantage of the Lightning routes built for Bitcoin (or any stablecoin with enough broad adoption) to be exchanged as assets at the edges with multi-hop transfers. Let us assume well-developed Lightning payment routes exist for Bitcoin, or any other token like a highly liquid stablecoin (let us say S-USD). Then, building an entirely new network for any other RAS token is unnecessary since any asset can use the BTC or S-USD routes as a backbone for its transactions. Imagine Alice wants to transfer a RAS utility token (let us call it UTL) to Eve for a value of 50$. Alice and Eve have no open Lightning channels between them with any token. However, Alice has an open channel with Bob in UTL, Bob has an open channel in BTC with Charlie, Charlie has an open channel in S-USD with Dave, and Dave, in turn, has an open channel with Eve in UTL. All channels have enough liquidity to allow a transfer of value for 50$ (though it is expressed in different tokens). At this point, Alice can use the route between Bob and Charlie in BTC and the route between Charlie and Dave in S-USD to transfer UTL to Dave. How does it work? Alice sends $50 worth of UTL to Bob in their Lightning channel. Bob charges Alice a small fee and sends Charlie $50 worth of BTC. Charlie charges a small fee and sends $50 worth of S-USD to Dave, who, in turn, charges a small fee and sends $50 worth of UTL to Eve. ![](https://lh3.googleusercontent.com/hL8TWCiqlmzQXs6HXTX59ZE3thLUj-yLn3msh1PFGui3qJ465NZvp4Awc2SEVELwLjghNG39Vp9NQXEb4ecGv-0x8pK-vCMLzOm-_epyUrxqR8XRftl7an4tk6spMKJMZwggPG7oPk-t14_pHnNv2Iw) At the end of the process, Bob, Charlie, and Dave each have more UTL, BTC, and S-USD, respectively, in their balance than before, but their total balance value in US dollars has not changed, except they earned a little routing fee paid by Alice. Alice successfully transferred UTL to Dave despite having no Lightning channel open between them in RAS tokens. Through this routing with “assets at the edges,” it is possible to route any number of assets, removing the need to bootstrap an entirely new network for any new asset. This allows for a broader multi-asset Lightning Network leveraging existing Bitcoin infrastructure. In the case above, UTL is at the edges, utilizing a pre-existing route in BTC on the Bitcoin network and S-USD on the Sequentia network. Another potentially revolutionary use case for the Lightning Network with RAS tokens is the high-frequency, low-cost peer-to-peer trading of stablecoins, utility, and security tokens against BTC or each other. The section dedicated to Lightning Network swaps (see §5.2) explains this in further detail. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sequentia.io/white-paper/4.-asset-tokenization/4.3.-lightning-network-payments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.