We use fuzzing and other techniques to find bugs, publishing them on this site along with advisories for security issues. We also write technical posts about our fuzzing tools and techniques.
Why
The Lightning Network’s four main implementations (LND, Core Lightning, LDK, and Eclair) all speak the same peer protocol. They have to interoperate with each other, and they have to hold up against a peer that is not playing along. Both of those are hard to get right, and neither is well covered by the tests a project writes for itself, which tend to assume a well-behaved peer.
That is the gap our tooling helps to address. Our fuzzing tools can play the role of a misbehaving peer, triggering unusual code paths and edge cases. This approach uncovers many kinds of issues, ranging from protocol violations to crashes and assertion failures, memory safety errors, and more.
Projects
smite is a coverage-guided snapshot fuzzer that drives all four implementations through the peer protocol.
What we publish
Every finding on this site traces back to one of our tools. Most were found by a tool directly. The rest are secondary findings: something discovered during development of the tool, variant analysis after a direct finding, or some other follow-up work motivated by one of our tools. A finding with no such trace belongs somewhere else, however good it is; there is far more Lightning Network security research than we could usefully republish.
Every advisory describes what led to the finding so that the link to our tools is clear.
Contact
For any problem with this site, including a correction to an advisory, create an issue on this site’s repository. Anything about one of our projects should be filed on that project’s own tracker, such as lnfuzz/smite.
Every page on this site names its own authors, who retain copyright in what they write.