rust-lightning/Cargo.toml

[package]
name = "lightning"
version = "0.0.4"
authors = ["Matt Corallo"]
license = "Apache-2.0"
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.
"""
build = "build.rs"

[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"]

[dependencies]
bitcoin = "0.13"
rust-crypto = "0.2"
rand = "0.4"
secp256k1 = "0.9"

[build-dependencies]
cc = "1.0"

[dev-dependencies.bitcoin]
version = "0.13"
features = ["bitcoinconsensus"]
initial checkin 2017-12-25 01:05:27 -05:00			`[package]`
			`name = "lightning"`
Bump version for API overhauls, update deps and docs 2018-07-19 22:45:34 -04:00			`version = "0.0.4"`
initial checkin 2017-12-25 01:05:27 -05:00			`authors = ["Matt Corallo"]`
Unify license with rust-bitcoin-spv 2018-03-05 15:08:43 -05:00			`license = "Apache-2.0"`
Fix repo link in Cargo 2018-04-26 17:34:55 -04:00			`repository = "https://github.com/rust-bitcoin/rust-lightning/"`
initial checkin 2017-12-25 01:05:27 -05:00			`description = """`
Bump version for API overhauls, update deps and docs 2018-07-19 22:45:34 -04:00			`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.`
initial checkin 2017-12-25 01:05:27 -05:00			`"""`
Provide fallback for crypto's fixed_time_eq on non-x86/arm targets 2018-04-16 16:55:03 -04:00			`build = "build.rs"`
initial checkin 2017-12-25 01:05:27 -05:00
			`[features]`
			`# Supports tracking channels with a non-bitcoin chain hashes. Currently enables all kinds of fun DoS attacks.`
			`non_bitcoin_chain_hash_routing = []`
Add some fuzz targets. Sadly none of them are really any good without some hand-holding to generate good input data, and unless sha256 gets stubbed out I'm not sure they're gonna get good without a symbolic execution fuzzer 2018-03-19 17:45:58 -04:00			`fuzztarget = ["secp256k1/fuzztarget", "bitcoin/fuzztarget"]`
initial checkin 2017-12-25 01:05:27 -05:00
			`[dependencies]`
Switch back to crates.io rust-bitcoin for 0.13 release 2018-04-16 20:33:39 -04:00			`bitcoin = "0.13"`
initial checkin 2017-12-25 01:05:27 -05:00			`rust-crypto = "0.2"`
Update deps, including significant dep reduction in rust-bitcoin! 2018-02-21 11:35:07 -05:00			`rand = "0.4"`
fuzztarget sha -> XOR, crates secp256k1 2018-04-26 19:44:24 -04:00			`secp256k1 = "0.9"`
Use libbitcoinconsensus to check tx validity in some tests 2018-04-02 18:28:50 -04:00
Provide fallback for crypto's fixed_time_eq on non-x86/arm targets 2018-04-16 16:55:03 -04:00			`[build-dependencies]`
Bump version for API overhauls, update deps and docs 2018-07-19 22:45:34 -04:00			`cc = "1.0"`
Provide fallback for crypto's fixed_time_eq on non-x86/arm targets 2018-04-16 16:55:03 -04:00
Use libbitcoinconsensus to check tx validity in some tests 2018-04-02 18:28:50 -04:00			`[dev-dependencies.bitcoin]`
			`version = "0.13"`
			`features = ["bitcoinconsensus"]`