mirrors/rust-lightning
1
0
Fork 0
mirror of https://github.com/lightningdevkit/rust-lightning.git synced 2025-02-25 15:20:24 +01:00
Code Issues Projects Releases Packages Wiki Activity
rust-lightning/lightning/Cargo.toml

45 lines
1.7 KiB
TOML
Raw Normal View History

Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
[package]
name = "lightning"
Bump versions to 0.0.14, lightning-invoice 0.5
2021-05-01 00:43:15 +00:00
version = "0.0.14"
Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
authors = ["Matt Corallo"]
Update licenses and add missing fields in Cargo.toml files
2021-03-09 16:51:14 -05:00
license = "MIT OR Apache-2.0"
Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
repository = "https://github.com/rust-bitcoin/rust-lightning/"
description = """
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.
"""
[features]
Add PersistenceNotifier to ChannelManager This will allow the ChannelManager to signal when it has new updates to persist, and adds a way for ChannelManager persisters to be notified when they should re-persist the ChannelManager to disk/backups. Feature-gate the wait_timeout function because the core lightning crate shouldn't depend on wallclock time unless users opt into it.
2020-11-19 12:53:16 -05:00
allow_wallclock_use = []
Expose test_utils to fuzztarget (in addition to _test_utils feature)
2020-11-25 17:50:38 -05:00
fuzztarget = ["bitcoin/fuzztarget", "regex"]
Introduce CommitmentTransaction, ChannelTransactionParameters CommitmentTransaction maintains the per-commitment transaction fields needed to construct the associated bitcoin transactions (commitment, HTLC). It replaces passing around of Bitcoin transactions. The ChannelKeys API is modified accordingly. By regenerating the transaction when implementing a validating external signer, this allows a higher level of assurance that all relevant aspects of the transactions were checked for policy violations. ChannelTransactionParameters replaces passing around of individual per-channel fields that are needed to construct Bitcoin transactions. Eliminate ChannelStaticData in favor of ChannelTransactionParameters. Use counterparty txid instead of tx in channelmonitor update.
2020-10-15 13:45:18 +02:00
# Internal test utilities exposed to other repo crates
Make _test_utils depend on bitcoinconsensus feature
2021-04-28 16:23:39 -04:00
_test_utils = ["hex", "regex", "bitcoin/bitcoinconsensus"]
Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
# Unlog messages superior at targeted level.
max_level_off = []
max_level_error = []
max_level_warn = []
max_level_info = []
max_level_debug = []
export "unsafe_revoked_tx_signing" feature Allows unsafe signing in dev code, such as functional testing of justice transactions outside our crate.
2020-07-03 13:41:21 -07:00
# Allow signing of local transactions that may have been revoked or will be revoked, for functional testing (e.g. justice tx handling).
# This is unsafe to use in production because it may result in the counterparty publishing taking our funds.
unsafe_revoked_tx_signing = []
Add a trivial benchmark of calculating routes on today's graph Sadly rust upstream never really figured out the benchmark story, and it looks like the API we use here may not be long for this world. Luckily, we can switch to criterion with largely the same API if that happens before upstream finishes ongoing work with the custom test framework stuff. Sadly, it requires fetching the current network graph, which I did using Val's route-testing script written to test the MPP router.
2021-02-15 16:49:02 -05:00
unstable = []
Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
[dependencies]
Update rust-bitcoin
2021-01-14 20:57:56 -05:00
bitcoin = "0.26"
Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
Put test utilities behind a feature flag. The utilities will still be part of cfg(test). The purpose of this is to enable other crates in the workspace to use the test utilities.
2020-09-16 17:27:13 -04:00
hex = { version = "0.3", optional = true }
regex = { version = "0.1.80", optional = true }
Use workspaces to separate crates
2019-11-15 02:44:30 +00:00
[dev-dependencies]
hex = "0.3"
Improve error message. ... for ChannelError and APIMisuseError Before this commit, When rl returns error, we don't know The actual parameter which caused the error. By returning parameterised `String` instead of predefined `&'static str`, We can give a caller improved error message. TestLogger now has two additional methods 1. `assert_log_contains` which checks the logged messsage has how many entry which includes the specified string as a substring. 2. `aasert_log_regex` mostly the same with `assert_log_contains` but it is more flexible that caller specifies regex which has to be satisfied instead of just a substring. For regex, tests now includes `regex` as dev-dependency.
2020-07-13 13:16:32 +09:00
regex = "0.1.80"
Add PersistenceNotifier to ChannelManager This will allow the ChannelManager to signal when it has new updates to persist, and adds a way for ChannelManager persisters to be notified when they should re-persist the ChannelManager to disk/backups. Feature-gate the wait_timeout function because the core lightning crate shouldn't depend on wallclock time unless users opt into it.
2020-11-19 12:53:16 -05:00
Make _test_utils depend on bitcoinconsensus feature
2021-04-28 16:23:39 -04:00
[dev-dependencies.bitcoin]
version = "0.26"
features = ["bitcoinconsensus"]
Add PersistenceNotifier to ChannelManager This will allow the ChannelManager to signal when it has new updates to persist, and adds a way for ChannelManager persisters to be notified when they should re-persist the ChannelManager to disk/backups. Feature-gate the wait_timeout function because the core lightning crate shouldn't depend on wallclock time unless users opt into it.
2020-11-19 12:53:16 -05:00
[package.metadata.docs.rs]
features = ["allow_wallclock_use"] # When https://github.com/rust-lang/rust/issues/43781 complies with our MSVR, we can add nice banners in the docs for the methods behind this feature-gate.
Reference in a new issue Copy permalink