Move ChannelMonitor state behind a Mutex

[rust-lightning] / Cargo.toml

diff --git a/Cargo.toml b/Cargo.toml
index bb00a9239269f502582430c8b13ecc50e8502963..1ffd75a8710494bd0694decc9bcb5e5ae03f6bfa 100644 (file)
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,25 +1,23 @@
-[package]
-name = "lightning"
-version = "0.0.2"
-authors = ["Matt Corallo"]
-license = "Apache-2.0"
-repository = "https://github.com/TheBlueMatt/rust-lightning/"
-description = """
-A Bitcoin Lightning implementation in Rust.
-Still super-early code-dump quality and is missing large chunks. See README in git repo 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 finish building it to even try.
-"""
+[workspace]
 
-[features]
-# Supports tracking channels with a non-bitcoin chain hashes. Currently enables all kinds of fun DoS attacks.
-non_bitcoin_chain_hash_routing = []
-fuzztarget = ["secp256k1/fuzztarget", "bitcoin/fuzztarget"]
+members = [
+    "lightning",
+    "lightning-block-sync",
+    "lightning-net-tokio",
+    "lightning-persister",
+    "background-processor",
+]
 
-[dependencies]
-bitcoin = "0.13"
-rust-crypto = "0.2"
-rand = "0.4"
-secp256k1 = "0.9"
+# Our tests do actual crypo and lots of work, the tradeoff for -O1 is well worth it.
+# Ideally we would only do this in profile.test, but profile.test only applies to
+# the test binary, not dependencies, which means most of the critical code still
+# gets compiled as -O0. See
+# https://doc.rust-lang.org/cargo/reference/profiles.html#profile-selection
+[profile.dev]
+opt-level = 1
+panic = "abort"
 
-[dev-dependencies.bitcoin]
-version = "0.13"
-features = ["bitcoinconsensus"]
+[profile.release]
+opt-level = 3
+lto = true
+panic = "abort"