{"release":{"id":"7a41a2cc5aaf78412593b2d310cf279f6d209fcbf373aa170d236de8b21d8f21","published":"2026-11-17T06:41:06Z","pinned":false},"limits":{"coverage":{"history":"current_only","held_since":"2026-05-22","gaps":[],"covered":["EBA Q&A 2024_7172 — Q&A — Lightning Network: TFR/Travel Rule scope for CASPs [Final Q&A] L3"],"not_covered":["national guidance","court decisions"]},"freshness":{"release_id":"7a41a2cc5aaf78412593b2d310cf279f6d209fcbf373aa170d236de8b21d8f21","release_published":"2026-11-17T06:41:06Z","checked_at":"2026-11-16","checked_against":"the EBA publication"},"truncation":null,"failures":[],"incomplete":[]},"page":{"path":"/mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule","url":"https://www.headlesslaw.com/mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule","title":"EBA Q&A 2024_7172 — Q&A — Lightning Network: TFR/Travel Rule scope for CASPs [Final Q&A]","family":"l3","work_id":"mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule","status":"final q&a","force_status":null,"date_state":"current","requested_date":null,"as_of":"2026-11-18","applies_from":null,"application":null,"version_label":"EBA Q&A register, 22 May 2026","check":{"against":"the EBA publication","on":"2026-11-16"},"check_result":"matched","official_url":"https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7172","valid_from":null,"valid_until":null,"revision":1,"content_id":"7f182d80b29f19ac","change_date":null,"nearest_versions":["2026-05-22"],"first_text_date":null,"correction_applies":false,"versions":["2026-05-22"],"version_url":"https://www.headlesslaw.com/mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule/versions/2026-05-22","revision_url":"https://www.headlesslaw.com/mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule/versions/2026-05-22/rev/7f182d80b29f19ac","versions_url":"https://www.headlesslaw.com/mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule/versions","relations_url":"https://www.headlesslaw.com/mica/level-3/q-and-a/eba/eba-qa-7172-lightning-network-travel-rule/relations","source_line":"Answer prepared by the European Commission, published in the EBA Q&A tool · not legislation · published 22 May 2026 [Final Q&A]","attribution":{"prepared_by":"European Commission","published_by":"EBA","published_in":"EBA Single Rulebook Q&A tool","document_type":"qa_answer","legal_nature":"not_legislation","addressees":"not stated in the document","dates":{"published_on":"2026-05-22","question_submitted_on":"2024-08-15","locators":{"published_on":"EBA Q&A register entry 2024_7172, field 'Final publishing date'","question_submitted_on":"EBA Q&A register entry 2024_7172, field 'Submission date'"}},"adoption":null}},"provenance":{"official_url":"https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7172","check":{"result":"matched","checked_at":"2026-11-16","against":"the EBA publication"},"repo_path":null,"body_sha256":"36beb3d5d3a5194203b47f96aeda9965897a953444671b9e2895b3a0296e6c4d","markdown_sha256":"dcaa06926412306bdd014e6d64b95e3ad23a48665c123128bdf02bc0292aac78"},"units":[],"markdown":"**Answer prepared by the European Commission, published in the EBA Q&A tool · not legislation · published 22 May 2026 [Final Q&A]**\n\n*Final Q&A · EBA Q&A register, 22 May 2026 · Verified 16 Nov 2026 · [Official source](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7172)*\n\n| | |\n|---|---|\n| **Full title** | EBA Q&A 2024_7172 — Q&A — Lightning Network: TFR/Travel Rule scope for CASPs \\[Final Q&A\\] |\n| **Prepared by** | European Commission |\n| **Published by** | EBA, in the EBA Single Rulebook Q&A tool |\n| **Reference** | EBA\\_QA\\_2024\\_7172 |\n| **Document type** | Q&A |\n| **Legal nature** | Not legislation |\n| **Addressees** | Not stated in the document |\n| **Dates** | Published 22 May 2026; question submitted 15 August 2024 |\n| **Legal basis** | WTR II [Articles 2(1)](https://www.headlesslaw.com/tofr/articles/2), [3](https://www.headlesslaw.com/tofr/articles/3); [MiCA](https://www.headlesslaw.com/) Article 3 |\n| **Related instruments** | None recorded |\n| **Text on this page** | Word for word — the full text of the EBA publication |\n\n**Lightning Network (LN) Transactions and whether they fall within the scope of the TFR and Travel Rule Guidelines.**\n\n### Question\n\nDo transactions on the Lightning Network fall within the scope of the TFR and Travel Rule Guidelines?\n\n### Background\n\nThe Lightning Network (LN) is a scaling solution based on the Bitcoin blockchain, also called a Layer 2-solution. It is a decentralized network using smart contract functionality in the blockchain to enable instant (micro)payments across a network of nodes. Two nodes can open a payment channel: a peer-to-peer connection through which bitcoin can be transacted. In their channel, they can transact as fast and often as they want by simply updating their private record. And when they are done, they can close the channel by settling the original on-chain transaction. Only this settlement will be visible on the blockchain. Each node can open as many channels with as many nodes as they want, forming a global web of connections. Through this web, nodes can ‘route’ payments to other nodes, even if they are not directly connected. Nodes: Source: bitcoinvisuals.com Network Capacity Source: bitcoinvisuals.com The LN has been growing rapidly in recent years. This is evidenced in part by the number of nodes and the sum of the credits in all channels between these nodes (also called the capacity of the LN). See also the relevant visuals Bitcoin Lightning Network Nodes Chart - Bitcoin Visuals and Bitcoin Lightning Network Capacity Chart - Bitcoin Visuals.\n\nThe LN has gained a foothold worldwide with nodes on every continent. Furthermore, several CASPs have already integrated the option to send bitcoin via lightning to/from their platform. Whereas regular Bitcoin transactions are in principle completely transparent, as they are recorded in the blockchain, this is different for Lightning transactions. Lightning transactions between two lightning nodes take place off-chain, only at the opening and closing of a channel is an on-chain transaction made that reflects the channel’s beginning and end balance. Moreover, indirect lightning transactions that span multiple channels are not traceable in the blockchain.\n\nThis raises the question whether transactions on the LN fall within the scope of the TFR. If not, we foresee a potentially undesirable shift of transactions to the LN (and possibly other scaling solutions). Specifically with respect to the LN, the TFR does not, in our view, provide a conclusive answer as to whether LN-transactions fall within its scope. According to Article 2(1) TFR the Regulation applies to transfer of crypto-assets, where the crypto-asset service provider, or the intermediary crypto-asset service provider, of either the originator or the beneficiary has its registered office in the Union. The definition of ‘’transfer of crypto-assets’’ has been set out in Article 3(10) TFR. The given definition raises the question whether units transferred on the LN qualify as transfers of crypto-assets. In our view, the TFR does not provide a conclusive answer to that question.\n\nPlease note that this uncertainty about whether Lightning Network transactions fall under the scope of TFR applies to other layer 2 and 3 solutions, as well.\n\n***\n\n### Answer\n\nThe Lightning Network (LN) is “a decentralized network using smart contract functionality in the blockchain to enable instant (micro)payments across a network of nodes. Two nodes can open a payment channel: a peer-to-peer connection through which bitcoin can be transacted”.\n\nRegulation (EU) 2013/1113 (TFR) applies to “transfers of crypto- assets, including transfers of crypto-assets executed by means of crypto-ATMs, where the [crypto-asset service provider](https://www.headlesslaw.com/definitions/mica/crypto-asset-service-provider), or the intermediary crypto-asset service provider, of either the originator or the beneficiary has its registered office in the Union” (article 2(1) TFR).\n\nTherefore, TFR only applies when at least one [crypto-asset service provider](https://www.headlesslaw.com/definitions/mica/crypto-asset-service-provider) (CASP) is involved in the transfer of crypto-assets. The notions of “crypto-asset” and CASP are defined in [articles 3(14)](https://www.headlesslaw.com/tofr/articles/3) and [3(15)](https://www.headlesslaw.com/tofr/articles/3) TFR by reference to [Regulation (EU) 2023/1114](https://www.headlesslaw.com/) ([MiCAR](https://www.headlesslaw.com/)).\n\nThe use of the LN does not seem to require the intermediation of CASPs for allowing transactions.\n\nAs clarified in recital 22 MiCAR, [crypto-asset services](https://www.headlesslaw.com/definitions/mica/crypto-asset-service) provided in a fully decentralised manner without any intermediary do not fall within the scope of MiCAR, and consequently they don’t fall either in the scope of the TFR.\n\nHowever, the submitter explains that “several CASPs have already integrated the option to send bitcoin via lightning to/from their platform. Whereas regular Bitcoin transactions are in principle completely transparent, as they are recorded in the blockchain, this is different for Lightning transactions. Lightning transactions between two lightning nodes take place off-chain, only at the opening and closing of a channel is an on-chain transaction made that reflects the channel’s beginning and end balance. Moreover, indirect lightning transactions that span multiple channels are not traceable in the blockchain”.\n\nThe operation of trading platforms by CASPs constitute a ‘[crypto-asset service](https://www.headlesslaw.com/definitions/mica/crypto-asset-service)’ for which CASPs must be authorised under MiCAR. This activity involves “the management of one or more multilateral systems, bringing together multiple third parties exchanging crypto-assets for [funds](https://www.headlesslaw.com/definitions/mica/funds) or for other crypto-assets”, as well as the “[exchange of crypto-assets for funds](https://www.headlesslaw.com/definitions/mica/exchange-of-crypto-assets-for-funds) and for other crypto-assets” and the “[execution of orders for crypto-assets on behalf of clients](https://www.headlesslaw.com/definitions/mica/execution-of-orders-for-crypto-assets-on-behalf-of-clients)”.\n\nConsequently, CASPs offering their customers the possibility to transfer crypto-assets with the use of the LN fall within the scope of MiCAR and TFR and should therefore comply with the travel rule requirements (i.e. before initiating or executing any transfer of crypto-assets, CASPs need to ensure that such transfers are accompanied by the relevant information on the originator and the beneficiary). By contrast, the same use of the LN in mere peer to peer transactions not operated by CASPs, does not fall within the scope of MiCAR (recital 22 MiCAR), nor that of the TFR.\n\nDisclaimer: This answer clarifies provisions already contained in the applicable legislation. They do not extend in any way the rights and obligations deriving from such legislation, nor do they introduce any additional requirements for the concerned operators and competent authorities. The answers are merely intended to assist natural or legal persons, including competent authorities and Union institutions and bodies in clarifying the application or implementation of the relevant legal provisions. Only the Court of Justice of the European Union is competent to authoritatively interpret Union law. The views expressed in the internal Commission Decision cannot prejudge the position that the European Commission might take before the Union and national courts.\n\n***\n\n**Source:** [EBA Single Rulebook Q\\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7172)\n\n### Related\n\n* [execution of orders for crypto-assets on behalf of clients](https://www.headlesslaw.com/definitions/mica/execution-of-orders-for-crypto-assets-on-behalf-of-clients) — defined term used on this page\n* [exchange of crypto-assets for funds](https://www.headlesslaw.com/definitions/mica/exchange-of-crypto-assets-for-funds) — defined term used on this page\n* [crypto-asset service provider](https://www.headlesslaw.com/definitions/mica/crypto-asset-service-provider) — defined term used on this page\n* [crypto-asset service](https://www.headlesslaw.com/definitions/mica/crypto-asset-service) — defined term used on this page\n\n## Related Level 1 articles\n\n- [Article 3 — Definitions](https://www.headlesslaw.com/mica/articles/3)\n"}