#bitcoin #github-issues #error-handling #try

no-std lightning

A Bitcoin Lightning library in Rust. Does most of the hard work, without implying a specific runtime, requiring clients implement basic network logic, chain interactions and disk storage. Still missing tons of error-handling. See GitHub issues for suggested projects if you want to contribute. Don't have to bother telling you not to use this for anything serious, because you'd have to build a client around it to even try.

29 releases

0.0.113 Dec 16, 2022
0.0.112 Oct 25, 2022
0.0.111 Sep 13, 2022
0.0.110 Jul 26, 2022
0.0.1 Feb 16, 2018

#1153 in Magic Beans

Download history 1063/week @ 2022-10-11 1855/week @ 2022-10-18 1937/week @ 2022-10-25 1542/week @ 2022-11-01 2071/week @ 2022-11-08 2061/week @ 2022-11-15 1059/week @ 2022-11-22 1034/week @ 2022-11-29 1367/week @ 2022-12-06 1584/week @ 2022-12-13 1952/week @ 2022-12-20 1645/week @ 2022-12-27 2200/week @ 2023-01-03 1429/week @ 2023-01-10 1928/week @ 2023-01-17 1648/week @ 2023-01-24

7,651 downloads per month
Used in 19 crates (11 directly)


64K SLoC

Rust-Lightning, not Rusty's Lightning!

A full-featured but also flexible lightning implementation, in library form. This allows the user (you) to decide how they wish to use it instead of being a fully self-contained daemon. This means there is no built-in threading/execution environment and it's up to the user to figure out how best to make networking happen/timers fire/things get written to disk/keys get generated/etc. This makes it a good candidate for tight integration into an existing wallet instead of having a rather-separate lightning appendage to a wallet.

default features are:

  • std - enables functionalities which require std, including std::io trait implementations and things which utilize time
  • grind_signatures - enables generation of low-r bitcoin signatures, which saves 1 byte per signature in 50% of the cases (see bitcoin PR #13666)

Available features are:

  • std
  • grind_signatures
  • no-std - exposes write trait implementations from the core2 crate (at least one of no-std or std are required)
  • Skip logging of messages at levels below the given log level:
    • max_level_off
    • max_level_error
    • max_level_warn
    • max_level_info
    • max_level_debug
    • max_level_trace


~98K SLoC