Discover the Lightning Network from a technical perspective
Introduction
Access 1ML and understand the home page
- The total number of active nodes on the network, i.e. the computers involved in sending and receiving Lightning payments.
- The number of open channels, which correspond to the connections between these nodes enabling funds transfers.
- The total network capacity, expressed in bitcoin (BTC), which indicates the sum of the capacities of all public channels.
- The most connected nodes, which have the most open channels to other nodes.
- The highest capacities on the nodes, indicating which nodes can transfer the largest amounts.
- The most important channels in terms of capacity.
Exploring Lightning nodes
- Node ID**: this unique identifier is a long string of characters that allows the node to be precisely identified throughout the network.
- Alias**: this is the name chosen by the node owner to represent it publicly.
- The number of channels indicates how many connections the node has open with other nodes, while the total capacity represents the sum of bitcoins available in these channels. A node with a large number of channels and high capacity is generally well connected and capable of transferring large amounts of money quickly across the network.
- The uptime, or availability, measures how long a node has remained active and accessible online, reflecting its reliability. The age of the node, on the other hand, indicates how long it has been present on the network, reflecting its stability and experience within Lightning Network.
Exploring lightning channels
What is a Lightning channel?
Read channel information on 1ML
- Partner nodes**: each channel links two nodes. 1ML displays both identifiers and their respective aliases.
- Channel capacity**: this is the total amount of bitcoins locked in this channel. This capacity represents the maximum limit of payments that can transit through this channel.
- Channel age**: indicates how long the channel has been open. An old channel is often a sign of a stable relationship between two nodes.
Channel visibility limits
Explore Lightning Network by location
Nodes by country and region
What this says about local adoption
- Technology adoption**: A large number of nodes in a region indicates that Bitcoin users, companies or services are actively adopting Lightning Network. This shows technological maturity and a willingness to take advantage of Lightning's benefits (fast transactions, lower costs).
- Economic ecosystem** : The dense presence of nodes can also signal a local economic fabric around Bitcoin: merchants accepting Lightning, startups developing tools, community events, etc.
- Security and resilience**: Diverse geographical distribution enhances network resilience in the face of local outages or restrictions. The more dispersed the nodes, the more decentralized and difficult to censor the network.
- Policies and regulations**: Some countries may see faster adoption thanks to a favorable regulatory framework or a proactive community. Conversely, in areas where regulations are strict or hostile, the number of nodes will be lower.
Limits of geographic data
- Approximate IP location**: 1ML generally uses the public IP address of nodes to estimate their location. However, this method can be distorted by the use of VPNs, cloud servers (AWS, Google Cloud), or hosting in countries different from the node owner's actual domicile.
- Virtual nodes**: Some operators host their nodes on remote servers for reasons of reliability and availability, which can give a false sense of physical location.
- User mobility**: A node operator may change location, move his infrastructure, or open several nodes in different regions, making data reading more complex.
- Invisibility of private nodes**: Some nodes don't publish their IP address or use methods to hide their location, making geolocation impossible.
1ML concrete use cases
Understanding network topology
Identify important nodes
Check the public visibility of a node
Watching Lightning Network evolve over time
1ML best practices and limitations
Public data ≠ complete reality
Privacy and Lightning
Don't jump to conclusions
Complementarity with other tools
1ML connection option (advanced functionality)
Conclusion
Author
This tutorial has been written by Béni-Christ
You can say thanks by tipping the professor.
Hello! I am a frontend developer, with a curious mind and a passion for learning. Since 2024, I have been interested in finance, blockchain, and Bitcoin. Now, I want to take the next step: sharing my knowledge and contributing to projects that connect technology and education.
Credits
This tutorial has not been proofread yet
The original content has been translated by AI, but human review is necessary to ensure its accuracy.
2 790 sats1 395 sats698 satsEvery content on the platform is the result of a collaborative effort: each lesson, translation, and revision is made possible by the work of contributors. For this reason, we are always looking for proofreaders who can review our content in many languages. If you want to participate in the proofreading process, please reach out in our Telegram group and read our tutorial. We remind you that this content is open-source - licensed under CC BY-SA - so it can be freely shared and used, as long as the original source is credited.

