milksad
/
rust-bitcoin-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity
rust-bitcoin-unsafe-fast/Cargo.toml

61 lines
2.2 KiB
TOML
Raw Normal View History

Initial commit, move into Cargo
2014-07-18 13:56:17 +00:00
[package]
Change name to `bitcoin` in Cargo.toml (copying convention from toml-rs and color-rs)
2014-07-18 19:07:10 +00:00
name = "bitcoin"
0.28.0-rc.1 release
2022-01-16 10:46:58 +00:00
version = "0.28.0-rc.1"
Initial commit, move into Cargo
2014-07-18 13:56:17 +00:00
authors = ["Andrew Poelstra <apoelstra@wpsoftware.net>"]
Move secp256k1 lib from sipa's (long expired) repo to the bitcoin one
2015-05-20 18:14:21 +00:00
license = "CC0-1.0"
update docs and github links for transfer to rust-bitcoin org
2018-03-05 19:44:44 +00:00
homepage = "https://github.com/rust-bitcoin/rust-bitcoin/"
repository = "https://github.com/rust-bitcoin/rust-bitcoin/"
Update documentation URL in Cargo.toml
2018-04-11 19:13:43 +00:00
documentation = "https://docs.rs/bitcoin/"
Move secp256k1 lib from sipa's (long expired) repo to the bitcoin one
2015-05-20 18:14:21 +00:00
description = "General purpose library for using and interoperating with Bitcoin and other cryptocurrencies."
keywords = [ "crypto", "bitcoin" ]
readme = "README.md"
exclude test_data when publishing the crate
2021-12-31 10:46:15 +00:00
exclude = ["./test_data"]
Move secp256k1 lib from sipa's (long expired) repo to the bitcoin one
2015-05-20 18:14:21 +00:00
Document cargo features This documents cargo features in two ways: explictly in text and in code using `#[doc(cfg(...))]` attribute where possible. Notably, this is impossible for `serde` derives. The attribute is contitional and only activated for docs.rs or explicit local builds. This change also adds `package.metadata.docs.rs` field to `Cargo.toml` which instructs docs.rs to build with relevant features and with `docsrs` config activated enabling `#[doc(cfg(...))] attributes. I also took the opportunity to fix a few missing spaces in nearby code.
2021-07-28 19:38:58 +00:00
# Please don't forget to add relevant features to docs.rs below
integration with bitcoinconsenus
2018-03-10 14:35:49 +00:00
[features]
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
default = [ "std", "secp-recovery" ]
Add MessageSignature type for dealing with signed messages
2020-10-07 15:46:48 +00:00
base64 = [ "base64-compat" ]
Add feature gated hex decode benchmark
2019-01-07 21:43:23 +00:00
unstable = []
Update secp256k1's rand feature to rand-std
2020-01-09 11:11:49 +00:00
rand = ["secp256k1/rand-std"]
Remove the hex dependency
2020-01-08 17:02:30 +00:00
use-serde = ["serde", "bitcoin_hashes/serde", "secp256k1/serde"]
Expose features of secp256k1
2020-09-24 10:59:43 +00:00
secp-lowmemory = ["secp256k1/lowmemory"]
Add MessageSignature type for dealing with signed messages
2020-10-07 15:46:48 +00:00
secp-recovery = ["secp256k1/recovery"]
integration with bitcoinconsenus
2018-03-10 14:35:49 +00:00
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
# At least one of std, no-std must be enabled.
#
# The no-std feature doesn't disable std - you need to turn off the std feature for that by disabling default.
# Instead no-std enables additional features required for this crate to be usable without std.
# As a result, both can be enabled without conflict.
std = ["secp256k1/std", "bitcoin_hashes/std", "bech32/std"]
Enable secp256k1/alloc for no-std
2021-08-02 07:55:37 +00:00
no-std = ["hashbrown", "core2/alloc", "bitcoin_hashes/alloc", "secp256k1/alloc"]
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
Document cargo features This documents cargo features in two ways: explictly in text and in code using `#[doc(cfg(...))]` attribute where possible. Notably, this is impossible for `serde` derives. The attribute is contitional and only activated for docs.rs or explicit local builds. This change also adds `package.metadata.docs.rs` field to `Cargo.toml` which instructs docs.rs to build with relevant features and with `docsrs` config activated enabling `#[doc(cfg(...))] attributes. I also took the opportunity to fix a few missing spaces in nearby code.
2021-07-28 19:38:58 +00:00
[package.metadata.docs.rs]
features = [ "std", "secp-recovery", "base64", "rand", "use-serde", "bitcoinconsensus" ]
Fixed docs.rs metadata This changes `rustc-args`, which doesn't do what we want, to `rustdoc-args`, which does.
2021-12-17 12:49:54 +00:00
rustdoc-args = ["--cfg", "docsrs"]
Document cargo features This documents cargo features in two ways: explictly in text and in code using `#[doc(cfg(...))]` attribute where possible. Notably, this is impossible for `serde` derives. The attribute is contitional and only activated for docs.rs or explicit local builds. This change also adds `package.metadata.docs.rs` field to `Cargo.toml` which instructs docs.rs to build with relevant features and with `docsrs` config activated enabling `#[doc(cfg(...))] attributes. I also took the opportunity to fix a few missing spaces in nearby code.
2021-07-28 19:38:58 +00:00
Some more renames for librustc changes
2015-03-26 15:44:49 +00:00
[dependencies]
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
bech32 = { version = "0.8.1", default-features = false }
bitcoin_hashes = { version = "0.10.0", default-features = false }
Update to secp256k1 0.21.2
2022-01-03 02:52:44 +00:00
secp256k1 = { version = "0.21.2", default-features = false }
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
core2 = { version = "0.3.0", optional = true, default-features = false }
Release v0.23.0
2020-01-07 19:27:05 +00:00
Replace serde_struct_impl with derive-based impls
2020-10-25 18:03:20 +00:00
base64-compat = { version = "1.0.0", optional = true }
Updating dependency versions
2021-05-04 01:13:52 +00:00
bitcoinconsensus = { version = "0.19.0-3", optional = true }
Replace serde_struct_impl with derive-based impls
2020-10-25 18:03:20 +00:00
serde = { version = "1", features = [ "derive" ], optional = true }
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
hashbrown = { version = "0.8", optional = true }
upgrade to secp256k1 0.15 and bitcoinconsensus 0.17
2019-07-27 07:28:51 +00:00
Add Amount and SignedAmount types
2018-11-10 00:45:00 +00:00
[dev-dependencies]
Restrict serde-json dev dependency to less than 1.0.45
2020-01-23 09:45:59 +00:00
serde_json = "<1.0.45"
Add Amount and SignedAmount types
2018-11-10 00:45:00 +00:00
serde_test = "1"
Update to secp256k1 0.21.2
2022-01-03 02:52:44 +00:00
secp256k1 = { version = "0.21.2", features = [ "recovery", "rand-std" ] }
Use efficient serialization for non-human-readable formats
2021-01-05 22:01:21 +00:00
bincode = "1.3.1"
Fix #430: ruy rust 1.22 inccompatibility
2020-06-01 12:44:39 +00:00
# We need to pin ryu (transitive dep from serde_json) to stay compatible with Rust 1.22.0
ryu = "<1.0.5"
no_std support Based on the original work by Justin Moon. *MSRV unchanged from 1.29.0.* When `std` is off, `no-std` must be on, and we use the [`alloc`](https://doc.rust-lang.org/alloc/) and core2 crates. The `alloc` crate requires the user define a global allocator. * Import from `core` and `alloc` instead of `std` * `alloc` only used if `no-std` is on * Create `std` feature * Create `no-std` feature which adds a core2 dependency to polyfill `std::io` features. This is an experimental feature and should be used with caution. * CI runs tests `no-std` * MSRV for `no-std` is 1.51 or so
2021-06-09 10:34:44 +00:00
[[example]]
name = "bip32"
[[example]]
name = "handshake"
required-features = ["std"]