Track actions to execute after a `ChannelMonitor` is updated

[rust-lightning] / Cargo.toml

diff --git a/Cargo.toml b/Cargo.toml
index 072f5a3a9746963e384657d2ab94ec6eff70414d..be76477f4c0f0548121cc8f5770053e798bbd3d0 100644 (file)
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,21 +1,36 @@
-[package]
-name = "lightning"
-version = "0.0.1"
-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"]
+members = [
+    "lightning",
+    "lightning-block-sync",
+    "lightning-transaction-sync",
+    "lightning-invoice",
+    "lightning-net-tokio",
+    "lightning-persister",
+    "lightning-background-processor",
+    "lightning-rapid-gossip-sync"
+]
 
-[dependencies]
-bitcoin = "0.12"
-rust-crypto = "0.2"
-rand = "0.4"
-secp256k1 = "0.9"
+exclude = [
+    "lightning-custom-message",
+    "no-std-check",
+]
+
+# Our tests do actual crypto 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"
+
+[profile.release]
+opt-level = 3
+lto = true
+panic = "abort"
+
+[profile.bench]
+opt-level = 3
+codegen-units = 1
+lto = true