|
18 | 18 | //! generated/etc. This makes it a good candidate for tight integration into an existing wallet
|
19 | 19 | //! instead of having a rather-separate lightning appendage to a wallet.
|
20 | 20 | //!
|
21 |
| -//! Available features are: |
22 |
| -//! |
23 |
| -//! 1. Skip logging of messages at levels below the given log level: |
24 |
| -//! * `max_level_off` |
25 |
| -//! * `max_level_error` |
26 |
| -//! * `max_level_warn ` |
27 |
| -//! * `max_level_info` |
28 |
| -//! * `max_level_debug` |
29 |
| -//! * `max_level_trace` |
30 |
| -//! |
31 |
| -//! 2. Allow signing of local transactions that may have been revoked or will be revoked, |
32 |
| -//! for functional testing (e.g. justice tx handling): |
33 |
| -//! * `unsafe_revoked_tx_signing` - allows unsafe signing in dev code, such as functional testing of justice transactions outside our crate |
34 |
| -//! * `_bench_unstable` - allows test features for benching |
35 |
| -//! * `no-std ` - exposes write trait implementations from the `core2` crate |
36 |
| -//! |
37 | 21 | //! `default` features are:
|
38 | 22 | //!
|
39 |
| -//! * `std` - enables things which require `std`, including `std::io` trait implementations and things which utilize time |
| 23 | +//! * `std` - enables functionalities which require `std`, including `std::io` trait implementations and things which utilize time |
40 | 24 | //! * `grind_signatures` - enables generation of [low-r bitcoin signatures](https://bitcoin.stackexchange.com/questions/111660/what-is-signature-grinding), which saves 1 byte per signature in 50% of the cases (see [bitcoin PR #13666](https://github.com/bitcoin/bitcoin/pull/13666))
|
41 | 25 | //!
|
| 26 | +//! Available features are: |
| 27 | +//! |
| 28 | +//! * `std` |
| 29 | +//! * `grind_signatures` |
| 30 | +//! * `no-std ` - exposes write trait implementations from the `core2` crate |
| 31 | +//! * `justice_tx_handling` - allows signing of local transactions that may have been revoked or will be revoked for functional testing |
| 32 | +//! * Skip logging of messages at levels below the given log level: |
| 33 | +//! * `max_level_off` |
| 34 | +//! * `max_level_error` |
| 35 | +//! * `max_level_warn ` |
| 36 | +//! * `max_level_info` |
| 37 | +//! * `max_level_debug` |
| 38 | +//! * `max_level_trace` |
| 39 | +
|
42 | 40 |
|
43 | 41 |
|
44 | 42 | #![cfg_attr(not(any(test, fuzzing, feature = "_test_utils")), deny(missing_docs))]
|
|
0 commit comments