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

75 lines
2.7 KiB
TOML
Raw Normal View History

Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[package]
name = "bitcoin"
bitcoin: Bump version number to v0.31.0 In preparation for release of v0.31.0 bump the version number. The changelog is already up to date because we have done two RC releases.
2023-10-24 04:28:08 +00:00
version = "0.31.0"
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
authors = ["Andrew Poelstra <apoelstra@wpsoftware.net>"]
license = "CC0-1.0"
repository = "https://github.com/rust-bitcoin/rust-bitcoin/"
documentation = "https://docs.rs/bitcoin/"
Improve manifest package section Improve all manifest package sections by doing: - Order the list of options uniformly - Remove unnecessary homepage option (currently same as repo) - Add categories section
2023-02-02 22:26:22 +00:00
description = "General purpose library for using and interoperating with Bitcoin."
categories = ["cryptography::cryptocurrencies"]
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
keywords = [ "crypto", "bitcoin" ]
bitcoin: Fix path to the readme We moved to a submodule and didn't fix the readme path in the `bitcoin` manifest.
2023-03-22 01:08:48 +00:00
readme = "../README.md"
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
edition = "2018"
Improve manifest package section Improve all manifest package sections by doing: - Order the list of options uniformly - Remove unnecessary homepage option (currently same as repo) - Add categories section
2023-02-02 22:26:22 +00:00
exclude = ["tests", "contrib"]
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[features]
default = [ "std", "secp-recovery" ]
rand-std should enable std Users should not need to specify both.
2023-10-04 06:09:26 +00:00
rand-std = ["secp256k1/rand-std", "std"]
Add rand-std feature Currently we enable "secp256k1/rand-std" in the "rand" feature, this is incorrect because it means "rand" implies "std" which it does not. Add a "rand-std" feature that turns on "seck256k1/rand-std" and make the "rand" feature turn on "seck256k1/rand".
2022-11-14 17:41:56 +00:00
rand = ["secp256k1/rand"]
Implement support for `alloc`-free parse errors This implements basic facilities to conditionally carry string inputs in parse errors. This includes: * `InputString` type that may carry the input and format it * `parse_error_type!` macro creating a special type for parse errors * `impl_parse` implementing parsing for various types as well as its `serde`-supporting alternative
2022-09-20 15:11:35 +00:00
serde = ["actual-serde", "hashes/serde", "secp256k1/serde", "internals/serde"]
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
secp-lowmemory = ["secp256k1/lowmemory"]
secp-recovery = ["secp256k1/recovery"]
Fix `no_std` when `bitcoinconsensus` is enabled `default-features = false` was missing previously but blindly adding it would lead to subtle risk of breaking when a crate not needing `std` depends on `bitcoinconsensus` and simultaneously another crate not needing `bitcoinconsensus` depends on `std` and another crate depends on them both. This change fixes it by introducing `bitcoinconsensus-std` feature flag and provides a fallback if the flag is off. Unfortunately the fallback has to use a bit of reasonable `unsafe` due to limitations of upcasting. The only safe alternatives are not do it and provide worse experience for crates that are affected by the problem above or break the API, which couldn't be backported and would be more annoying to use. Closes #1343
2022-10-25 11:35:32 +00:00
bitcoinconsensus-std = ["bitcoinconsensus/std", "std"]
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +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.
Add a `bitcoin_io` crate In order to support standard (de)serialization of structs, the `rust-bitcoin` ecosystem uses the standard `std::io::{Read,Write}` traits. This works great for environments with `std`, however sadly the `std::io` module has not yet been added to the `core` crate. Thus, in `no-std`, the `rust-bitcoin` ecosystem has historically used the `core2` crate to provide copies of the `std::io` module without any major dependencies. Sadly, its one dependency, `memchr`, recently broke our MSRV. Worse, because we didn't want to take on any excess dependencies for `std` builds, `rust-bitcoin` has had to have mutually-exclusive `std` and `no-std` builds. This breaks general assumptions about how features work in Rust, causing substantial pain for applications far downstream of `rust-bitcoin` crates. Here, we add a new `bitcoin_io` crate, making it an unconditional dependency and using its `io` module in the in-repository crates in place of `std::io` and `core2::io`. As it is not substantial additional code, the `hashes` io implementations are no longer feature-gated. This doesn't actually accomplish anything on its own, only adding the new crate which still depends on `core2`.
2023-10-04 05:51:26 +00:00
std = ["secp256k1/std", "bitcoin-io/std", "hashes/std", "bech32/std", "internals/std", "hex/std"]
Remove `core2` dependency entirely
2023-11-06 19:22:43 +00:00
no-std = ["hashes/alloc", "hashes/io", "bitcoin-io/alloc", "bech32/alloc", "secp256k1/alloc", "hex/alloc"]
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[package.metadata.docs.rs]
Fix docs.rs to use all features Many moon ago we were unable to build with `--all-features`, this is no longer the case. Instruct docs.rs to build the docs with `--all-features`.
2023-02-02 22:24:48 +00:00
all-features = true
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
rustdoc-args = ["--cfg", "docsrs"]
[dependencies]
Remove path field from internals dependency We use two different methods for specifying local dependencies, `patch` and also `path`. There does not seem to be a reason why we use both, lets be uniform. Elect to use `patch` for all local crates.
2023-06-27 22:57:25 +00:00
internals = { package = "bitcoin-internals", version = "0.2.0" }
Depend on hex-conservative We have just released the `hex-conservative` crate, we can now use it. Do the following: - Depend on `hex-conservative` in `bitcoin` and `hashes` - Re-export `hex-conservative` as `hex` from both crate roots. - Remove all the old hex code from `hashes` - Fix all the import statements (makes up the bulk of the lines changed in this patch)
2023-07-21 00:38:34 +00:00
hex = { package = "hex-conservative", version = "0.1.1", default-features = false }
Update bech32 dependency Update the `bech32` dependency to use the newly release beta version. The main fix here is silent, a bug fix in `bech32` that was being hit by our fuzzing suite.
2023-10-09 18:17:26 +00:00
bech32 = { version = "0.10.0-beta", default-features = false }
hashes: Bump version to 0.13.0 Add a changelog entry and bump the version to 0.13.0 Does not include changes to `bitcoin` to depend on the new version.
2023-07-14 04:45:33 +00:00
hashes = { package = "bitcoin_hashes", version = "0.13.0", default-features = false }
Upgrade the secp dependency Upgrade the `secp256k1` dependency to the newly released `v0.28.0`. FTR this includes two simple changes: - Use `Message::from_digest_slice` instead of `Message::from_slice`. - Use `secp256k1::Keypair` instead of `secp256k1::KeyPair`.
2023-10-02 01:48:50 +00:00
secp256k1 = { version = "0.28.0", default-features = false, features = ["hashes"] }
Put non-optional dependency with other non-optional We have a separation between optional dependencies and non-optional dependencies, `hex_lit` snuck in to the wrong group.
2023-02-20 21:33:51 +00:00
hex_lit = "0.1.1"
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
Add a `bitcoin_io` crate In order to support standard (de)serialization of structs, the `rust-bitcoin` ecosystem uses the standard `std::io::{Read,Write}` traits. This works great for environments with `std`, however sadly the `std::io` module has not yet been added to the `core` crate. Thus, in `no-std`, the `rust-bitcoin` ecosystem has historically used the `core2` crate to provide copies of the `std::io` module without any major dependencies. Sadly, its one dependency, `memchr`, recently broke our MSRV. Worse, because we didn't want to take on any excess dependencies for `std` builds, `rust-bitcoin` has had to have mutually-exclusive `std` and `no-std` builds. This breaks general assumptions about how features work in Rust, causing substantial pain for applications far downstream of `rust-bitcoin` crates. Here, we add a new `bitcoin_io` crate, making it an unconditional dependency and using its `io` module in the in-repository crates in place of `std::io` and `core2::io`. As it is not substantial additional code, the `hashes` io implementations are no longer feature-gated. This doesn't actually accomplish anything on its own, only adding the new crate which still depends on `core2`.
2023-10-04 05:51:26 +00:00
bitcoin-io = { version = "0.1", default-features = false }
Update base64 usage to 0.21.3
2023-08-28 00:02:58 +00:00
base64 = { version = "0.21.3", optional = true }
Add comment to bitcoinconsensus dependency Add a comment to point users towards the `bitcoinconsensus-std` feature for std builds.
2023-06-19 19:24:30 +00:00
# Only use this feature for no-std builds, otherwise use bitcoinconsensus-std.
Put optional = true at the end In order to be uniform and make it easier to quickly see that the dependency is optional put `optional = true` as the last item in the config set.
2023-02-20 21:35:25 +00:00
bitcoinconsensus = { version = "0.20.2-0.5.0", default-features = false, optional = true }
Add usage docs to the "core2" feature We do not expect users of `rust-bitcoin` to ever activate the "core2" dependency directly, add a comment explaining that.
2023-07-21 00:44:16 +00:00
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
# Do NOT use this as a feature! Use the `serde` feature instead.
Fix serde versions `Cargo.toml` claimed that this crate works with very old versions of `serde` which wasn't the case. This commit changes the versions to minimal known-to-work values.
2022-09-13 13:47:21 +00:00
actual-serde = { package = "serde", version = "1.0.103", default-features = false, features = [ "derive", "alloc" ], optional = true }
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[dev-dependencies]
Fix serde versions `Cargo.toml` claimed that this crate works with very old versions of `serde` which wasn't the case. This commit changes the versions to minimal known-to-work values.
2022-09-13 13:47:21 +00:00
serde_json = "1.0.0"
serde_test = "1.0.19"
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
bincode = "1.3.1"
Introduce mutation testing Introduce mutation testing by way of mutagen [0] - Conditionally add the dev-dependency `mutagen` (using `do_mutate` flag) This flag is not very well named but `mutagen` and `mutate` are already taken? - Mutate all methods of the `U256` struct that do not require additional unit tests. Uses `cfg(all(test, do_mutate), mutate)` - I cannot workout why we need to check on `test` as well i.e., I don't understand why we cannot use `cfg(do_mutate, mutate)`? With this applied test can be run as usual with a stable toolchain. To run mutagen we use `RUSTFLAGS='--cfg=do_mutate' cargo +nightly mutagen`. [0] https://github.com/llogiq/mutagen
2022-12-20 05:19:32 +00:00
[target.'cfg(mutate)'.dev-dependencies]
mutagen = { git = "https://github.com/llogiq/mutagen" }
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[[example]]
name = "bip32"
[[example]]
name = "handshake"
Remove rand-std dev-dependency from secp256k1 In order to get better test coverage we should not enable the secp26k1 feature "rand-std" in dev-dependencies but instead feature gate tests that depend on this feature.
2022-11-16 21:16:01 +00:00
required-features = ["std", "rand-std"]
Add a workspace to the top level directory. Create a directory `bitcoin` and move into it the following as is with no code changes: - src - Cargo.toml - contrib - test_data - examples Then do: - Add a workspace to the repository root directory. - Add the newly created `bitcoin` crate to the workspace. - Exclude `fuzz` and `embedded` crates from the workspace. - Add a contrib/test.sh script that runs contrib/test.sh in each sub-crate - Fix the bitcoin/contrib/test.sh script
2022-09-07 23:32:08 +00:00
[[example]]
name = "ecdsa-psbt"
required-features = ["std", "bitcoinconsensus"]
examples: Add taproot-psbt workflow example This example shows how to use the PSBT API for taproot transactions. We have a simple BIP86-style spend and an example of an inheritance timelock that can be spent either by the beneficiary via the script path after a timelock, or via the key path by the benefactor so that they can refresh the timelock at any time.
2022-05-07 20:22:53 +00:00
[[example]]
name = "taproot-psbt"
Remove rand-std dev-dependency from secp256k1 In order to get better test coverage we should not enable the secp26k1 feature "rand-std" in dev-dependencies but instead feature gate tests that depend on this feature.
2022-11-16 21:16:01 +00:00
required-features = ["std", "rand-std", "bitcoinconsensus"]