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

63 lines
2.3 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"
release 0.28.0
2022-04-05 20:39:13 +00:00
version = "0.28.0"
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"]
Enable edition 2018 Add 'edition = "2018"' to the manifest and do a bunch of manual path fixups (use statements and fully qualified paths).
2022-05-02 23:02:58 +00:00
edition = "2018"
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" ]
Update secp256k1's rand feature to rand-std
2020-01-09 11:11:49 +00:00
rand = ["secp256k1/rand-std"]
Feature `use-serde` renamed to `serde` Features activating external crates are supposed to have same name as those crates. However we depend on same feature in other crates so we need a separate feature. After MSRV bump it is possible to rename the crates and features so we can now fix this inconsistency. Sadly, derive can't see that the crate was renamed so all derives must be told to use the other one.
2022-05-25 06:41:59 +00:00
serde = ["actual-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]
Feature `use-serde` renamed to `serde` Features activating external crates are supposed to have same name as those crates. However we depend on same feature in other crates so we need a separate feature. After MSRV bump it is possible to rename the crates and features so we can now fix this inconsistency. Sadly, derive can't see that the crate was renamed so all derives must be told to use the other one.
2022-05-25 06:41:59 +00:00
features = [ "std", "secp-recovery", "base64", "rand", "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 }
Upgrade to bitcoin_hashes v0.11.0
2022-06-07 02:39:25 +00:00
bitcoin_hashes = { version = "0.11.0", default-features = false }
Upgrade to secp256k1 v0.23.0 We recently released a new version of `rust-secp256k1`, upgrade to use it.
2022-06-28 02:47:29 +00:00
secp256k1 = { version = "0.23.0", 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 base64-compat dependency Now that we have MSRV 1.41.1 we can use the more modern `base64` instead of the compat crate. Requires no changes other than changing the dependency.
2022-05-11 00:33:03 +00:00
base64 = { version = "0.13.0", optional = true }
Updating dependency versions
2021-05-04 01:13:52 +00:00
bitcoinconsensus = { version = "0.19.0-3", optional = true }
Feature `use-serde` renamed to `serde` Features activating external crates are supposed to have same name as those crates. However we depend on same feature in other crates so we need a separate feature. After MSRV bump it is possible to rename the crates and features so we can now fix this inconsistency. Sadly, derive can't see that the crate was renamed so all derives must be told to use the other one.
2022-05-25 06:41:59 +00:00
# Do NOT use this as a feature! Use the `serde` feature instead.
actual-serde = { package = "serde", version = "1", default-features = false, features = [ "derive", "alloc" ], 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"
Upgrade to secp256k1 v0.23.0 We recently released a new version of `rust-secp256k1`, upgrade to use it.
2022-06-28 02:47:29 +00:00
secp256k1 = { version = "0.23.0", features = [ "recovery", "rand-std" ] }
Use efficient serialization for non-human-readable formats
2021-01-05 22:01:21 +00:00
bincode = "1.3.1"
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"]
Add psbt example Add an example PSBT workflow. The workflow we simulate is that of a setup using a watch-only online wallet (contains only public keys) and a cold-storage wallet (contains the private keys). We create and update a PSBT using the watch-only wallet then pass the PSBT to the cold-storage wallet to sign. Co-authored-by: Dan Gould <d@ngould.dev>
2022-04-04 06:50:08 +00:00
[[example]]
name = "ecdsa-psbt"
required-features = ["std", "bitcoinconsensus"]