This book is a collaboration between Andreas M. Antonopoulos, Olaoluwa Osuntokun, and Rene Pickhardt.
The following typographical conventions are used in this book:
- Italic
-
Indicates new terms, URLs, email addresses, filenames, and file extensions.
- Constant width
-
Used for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.
Constant width bold
-
Shows commands or other text that should be typed literally by the user.
- Constant width italic
-
Shows text that should be replaced with user-supplied values or by values determined by context.
Tip
|
This element signifies a tip or suggestion. |
Note
|
This element signifies a general note. |
Warning
|
This element indicates a warning or caution. |
The examples are illustrated in Go, C++, Python, and using the command line of a Unix-like operating system. All code snippets are available in the GitHub repository under the code subdirectory. Fork the book code, try the code examples, or submit corrections via GitHub: https://github.com/lnbook/lnbook.
All the code snippets can be replicated on most operating systems with a minimal installation of compilers, interpreters, and libraries for the corresponding languages. Where necessary, we provide basic installation instructions and step-by-step examples of the output of those instructions.
Some of the code snippets and code output have been reformatted for print. In all such cases, the lines have been split by a backslash (\) character, followed by a newline character. When transcribing the examples, remove those two characters and join the lines again and you should see identical results to those shown in the example.
All the code snippets use real values and calculations where possible, so that you can build from example to example and see the same results in any code you write to calculate the same values. For example, the private keys and corresponding public keys and addresses are all real.
This book is here to help you get your job done. In general, if example code is offered with this book, you may use it in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.
We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, ISBN, and copyright. For example: “Mastering the Lightning Network by Andreas M. Antonopoulos, Olaoluwa Osuntokun, Rene Pickhardt (O’Reilly). Copyright 2020, ISBN - xxx-xx-x-xxxxx."
Mastering the Lightning Network is offered under the Creative Commons Attribution-Noncommercial-No Derivative Works 4.0 International License (CC BY-NC-ND 4.0).
If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at [email protected].
All references to companies and products are intended for educational, demonstration, and reference purposes. The authors do not endorse any of the companies or products mentioned. We have not tested the operation or security of any of the products, projects, or code segments shown in this book. Use them at your own risk!
The Bitcoin addresses, transactions, keys, QR codes, and blockchain data used in this book are, for the most part, real. That means you can browse the blockchain, look at the transactions offered as examples, retrieve them with your own scripts or programs, etc.
However, note that the private keys used to construct the addresses printed in this book have been "burned." This means that if you send money to any of these addresses, the money will either be lost forever or (more likely) appropriated, since anyone who reads the book can take it using the private keys printed herein.
Warning
|
DO NOT SEND MONEY TO ANY OF THE ADDRESSES IN THIS BOOK. Your money will be taken by another reader, or lost forever. |
Note
|
For almost 40 years, O’Reilly Media has provided technology and business training, knowledge, and insight to help companies succeed. |
Our unique network of experts and innovators share their knowledge and expertise through books, articles, conferences, and our online learning platform. O’Reilly’s online learning platform gives you on-demand access to live training courses, in-depth learning paths, interactive coding environments, and a vast collection of text and video from O’Reilly and 200+ other publishers. For more information, please visit http://oreilly.com.
Information about Mastering the Lightning Network as well as the Open Edition and translations are available at https://lnbook.info/.
Please address comments and questions concerning this book to the publisher:
- O’Reilly Media, Inc.
- 1005 Gravenstein Highway North
- Sebastopol, CA 95472
- 800-998-9938 (in the United States or Canada)
- 707-829-0515 (international or local)
- 707-829-0104 (fax)
Send comments or technical questions about this book to [email protected].
For more information about our books, courses, conferences, and news, see our website at https://www.oreilly.com.
Find us on Facebook: https://facebook.com/oreilly
Follow us on Twitter: https://twitter.com/oreillymedia
Watch us on YouTube: https://www.youtube.com/oreillymedia
You can contact Andreas M. Antonopoulos on his personal site: https://aantonop.com/
Subscribe to Andreas’s channel on YouTube: https://www.youtube.com/aantonop
Like Andreas’s page on Facebook: https://www.facebook.com/AndreasMAntonopoulos
Follow Andreas on Twitter: https://twitter.com/aantonop
Connect with Andreas on LinkedIn: https://linkedin.com/company/aantonop
Andreas would also like to thank all of the patrons who support his work through monthly donations. You can support Andreas on Patreon at https://patreon.com/aantonop.
You can contact Rene Pickhardt on his personal site: https://www.rene-pickhardt.de/
Subscribe to Rene’s channel on YouTube: https://www.youtube.com/user/RenePickhardt
Follow Rene on Twitter: https://twitter.com/renepickhardt
Connect with Rene on LinkedIn: https://www.linkedin.com/in/rene-pickhardt-80313744/
Rene would also like to thank all of the patrons who support his work through monthly donations. You can support Rene on Patreon at https://patreon.com/renepickhardt.
Or you can support his work directly with bitcoin (also via the Lightning Network) at https://tallyco.in/s/lnbook for which Rene is equally thankful as for his patreons.
I owe my love of words and books to my mother, Theresa, who raised me in a house with books lining every wall. My mother also bought me my first computer in 1982, despite being a self-described technophobe. My father, Menelaos, a civil engineer who published his first book at 80 years old, was the one who taught me logical and analytical thinking and a love of science and engineering.
Thank you all for supporting me throughout this journey.
I want to mainly thank all the students I ever taught and who engaged into interesting discussions and questions. Believe it or not from you I learnt the most. I am also grateful to the Bitcoin and Lightning Network community who welcomed me and supported my efforts. In particular I am grateful to all the open source Bitcoin and Lightning Network protocol developers and people who fund them to make that technology possible. Last but not least I am thankful to my loved ones.
Many contributors offered comments, corrections, and additions to the book as it was collaboratively written on GitHub.
Following is an alphabetically sorted list of all the GitHub contributors, including their GitHub IDs in parentheses:
-
8go (@8go)
-
Aaqil Aziz (@batmanscode)
-
Alexander Gnip (@quantumcthulhu)
-
Alpha Q. Smith (@alpha_github_id)
-
Brian L. McMichael (@brianmcmichael)
-
Darius E. Parvin (@DariusParvin)
-
Doru Muntean (@chriton)
-
Eduardo Lima III (@elima-iii)
-
Emilio Norrmann (@enorrmann)
-
Francisco Calderón (@grunch)
-
Giovanni Zotta (@GiovanniZotta)
-
Gustavo Silva (@GustavoRSSilva)
-
Haoyu Lin (@HAOYUatHZ)
-
Hatim Boufnichel (@boufni95)
-
Imran Lorgat (@ImranLorgat)
-
John Davies (@tigeryant)
-
Julien Wendling (@trigger67)
-
Kory Newton (@korynewton)
-
Luigi (@gin)
-
Omega X. Last (@omega_github_id)
-
Patrick Lemke (@PatrickLemke)
-
Paul Wackerow (@wackerow)
-
René Köhnke (@rene78)
-
Ricardo Marques (@RicardoM17)
-
Sebastian Falbesoner (@theStack)
-
Sergei Tikhomirov (@s-tikhomirov)
-
Simone Bovi (@SimoneBovi)
-
Taylor Masterson (@tjmasterson)
-
Umar Bolatov (@bolatovumar)
Without the help offered by everyone listed above, this book would not have been possible. Your contributions demonstrate the power of open source and open culture, and we are eternally grateful for your help.
Thank you.
This book references various public and open-licensed sources:
ION Lightning Network Wiki https://wiki.ion.radar.tech/
Lightning 101: What is a Lightning Invoice? by suredbits https://medium.com/suredbits/lightning-101-what-is-a-lightning-invoice-d527db1a77e6
Lightning Network Specifications Github https://github.com/lightningnetwork/lightning-rfc/:: Creative Commons Attribution (CC-BY 4.0)