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

82 lines
2.9 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"
Update to edition 2021 We just bumped the MSRV to Rust 1.56.1 which includes edition 2021. Update all crates in this repo to use edition 2021 and build/lint warnings.
2023-11-14 22:14:56 +00:00
edition = "2021"
Add rust-version to the workspace manifests Add `rust-version = 1.56.1` to all crates in the workspace i.e., including `fuzz` but excluding the various test crates.
2023-11-15 00:54:33 +00:00
rust-version = "1.56.1"
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" ]
Add a new base58 crate Add a new `base58` crate to the workspace and move the `bitcoin::base58` module to it. Done as part of crate smashing, specifically so that we can make `bip32` into a separate crate.
2024-02-15 03:35:29 +00:00
std = ["base58/std", "bech32/std", "hashes/std", "hex/std", "internals/std", "io/std", "secp256k1/std", "units/std"]
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"]
Add bitcoin-units crate Add a new crate `bitcoin-units`, move the `amount` module over to it and re-export all types from `bitcoin::amount` so this as not a breaking change.
2023-08-08 08:47:05 +00:00
serde = ["actual-serde", "hashes/serde", "secp256k1/serde", "internals/serde", "units/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
[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]
base58: Re-name crate to base58ck The current name `base58check` is taken, as is `base58`. Use `base58ck` instead. Add a brief section to the readme about the crate naming.
2024-02-25 21:43:46 +00:00
base58 = { package = "base58ck", version = "0.1.0", default-features = false }
Update bech32 dependency Update `bech32` to the newly released version `0.11.0`.
2024-02-26 04:31:51 +00:00
bech32 = { version = "0.11.0", default-features = false, features = ["alloc"] }
Remove no-std feature Currently `bitcoin` cannot be built with no features enabled, it must have either "no-std" or "std" enabled. This is an artifact from when we depended on `core2` for "no-std", now that we have our own `io` crate and we unconditionally depend on it we can remove the "no-std" feature.
2023-11-28 03:22:24 +00:00
hashes = { package = "bitcoin_hashes", version = "0.13.0", default-features = false, features = ["alloc", "io"] }
Upgrade hex dependency Upgrade to the new `hex v0.2.0` release.
2024-02-27 22:56:27 +00:00
hex = { package = "hex-conservative", version = "0.2.0", default-features = false, features = ["alloc"] }
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"
Re-order dependencies in manifest Currently the feature enabling is different for "std" and "no-std", which is again different to the order in the dependencies section. These two things make reading the manifest harder than it needs to be. Put the dependencies in alphabetic order in the dependencies section as well as when enabling them. Refactor only, no logic changes.
2023-11-28 02:56:45 +00:00
internals = { package = "bitcoin-internals", version = "0.2.0" }
io: Bump version to 0.1.1 We attempted to release with the current 0.1.0 version forgetting that we had previously released an empty crate with that version to reserve the name on crates.io. Bump the version to 0.1.1 and release the actual code.
2024-02-17 22:39:28 +00:00
io = { package = "bitcoin-io", version = "0.1.1", default-features = false, features = ["alloc"] }
Remove no-std feature Currently `bitcoin` cannot be built with no features enabled, it must have either "no-std" or "std" enabled. This is an artifact from when we depended on `core2` for "no-std", now that we have our own `io` crate and we unconditionally depend on it we can remove the "no-std" feature.
2023-11-28 03:22:24 +00:00
secp256k1 = { version = "0.28.0", default-features = false, features = ["hashes", "alloc"] }
Add bitcoin-units crate Add a new crate `bitcoin-units`, move the `amount` module over to it and re-export all types from `bitcoin::amount` so this as not a breaking change.
2023-08-08 08:47:05 +00:00
units = { package = "bitcoin-units", version = "0.1.0", default-features = false, features = ["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
Update base64 usage to 0.21.3
2023-08-28 00:02:58 +00:00
base64 = { version = "0.21.3", optional = true }
Implement ArbitaryOrd for absolute::LockTime At times we would like to provide types that do not implement `PartialOrd` and `Ord` because it does not make sense. I.e., we do not want users writing `a < b`. This could range from kind-of-iffy to down-right-buggy (like comparing absolute locktimes). However this decision effects downstream users who may not care about what the ordering means they just need to use it for some other reason e.g., to use as part of a key for a `BTreeMap` (as we do in `miniscript` requiring the `AbsLockTime` type). A solution to this problem is to provide a wrapper data type that adds `PartialOrd` and `Ord` implementations. I wrote the `ordered` crate is for this very purpose. Feature gate a new dependency on `ordered` and implement `ArbitraryOrd` for `absolute::LockTime`.
2023-12-01 21:50:51 +00:00
ordered = { version = "0.2.0", 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.
Upgrade bitcoinconsenus Upgrade to the most recent `bitcoinconsensus` version that excludes Taproot verification i.e., one version before latest.
2024-03-12 01:04:32 +00:00
bitcoinconsensus = { version = "0.105.0+25.1", 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
bitcoin: Add signing examples Add two signing examples to showcase signing a simple one input two output transaction using both segwit v0 outputs and taproot outputs. This patch is the result of the recent rust-bitcoin TABConf workshop, wit bug fix by Sanket, updated to use APIs from tip of master branch. This code, depending on v0.30.0 is what is being introduced to the cookbook at the moment.
2023-09-29 01:49:45 +00:00
[[example]]
name = "sign-tx-segwit-v0"
required-features = ["std", "rand-std"]
[[example]]
name = "sign-tx-taproot"
required-features = ["std", "rand-std"]
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"]
Run sighash example in CI Somehow we forgot to run the `sighash` example in CI.
2024-02-05 06:50:52 +00:00
[[example]]
name = "sighash"