rust-lightning/lightning-invoice
Matt Corallo 42ebf77415 Move Score into a scoring module instead of a top-level module
Traits in top-level modules is somewhat confusing - generally
top-level modules are just organizational modules and don't contain
things themselves, instead placing traits and structs in
sub-modules. Further, its incredibly awkward to have a `scorer`
sub-module, but only have a single struct in it, with the relevant
trait it is the only implementation of somewhere else. Not having
`Score` in the `scorer` sub-module is further confusing because
it's the only module anywhere that references scoring at all.
2021-11-16 20:58:37 +00:00
..
fuzz Bump dependencies to bitcoin 0.27 and bech32 0.8 2021-07-31 18:29:07 +00:00
src Move Score into a scoring module instead of a top-level module 2021-11-16 20:58:37 +00:00
tests Use new BOLT 11 test vectors with payment_secrets and feature flags 2021-08-31 21:29:51 +00:00
.gitignore Pure import of lightning-invoice crate 2021-04-09 10:08:27 -04:00
Cargo.toml Bump crate versions to 0.0.103/invoice 0.11 2021-11-03 02:20:51 +00:00
README.md Clean up lightning-invoice Cargo.toml and README 2021-04-09 10:08:27 -04:00

lightning-invoice

Docs.rs

This repo provides data structures for BOLT 11 lightning invoices and functions to parse and serialize these from and to bech32.

Please be sure to run the test suite since we need to check assumptions regarding SystemTime's bounds on your platform. You can also call check_platform on startup or in your test suite to do so.