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

update README to reflect 0.10, bump version to republish

This commit is contained in:
Andrew Poelstra 2017-12-13 21:20:16 +00:00
parent 9a498ad5e1
commit b7ec971541
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Cargo.toml
View File

@ -1,7 +1,7 @@
[package] [package]
name = "bitcoin" name = "bitcoin"
version = "0.10.4" version = "0.10.5"
authors = ["Andrew Poelstra <apoelstra@wpsoftware.net>"] authors = ["Andrew Poelstra <apoelstra@wpsoftware.net>"]
license = "CC0-1.0" license = "CC0-1.0"
homepage = "https://github.com/apoelstra/rust-bitcoin/" homepage = "https://github.com/apoelstra/rust-bitcoin/"

5
README.md
View File

@ -27,7 +27,7 @@ To use rust-bitcoin, just add the following to your Cargo.toml.
```toml ```toml
[dependencies] [dependencies]
bitcoin = "0.9" bitcoin = "0.10"
``` ```
# Known limitations # Known limitations
@ -43,6 +43,9 @@ based cryptocurrency such as Bitcoin it is critical that all parties are
using the same rules to validate data, and this library is simply unable using the same rules to validate data, and this library is simply unable
to implement the same rules as Core. to implement the same rules as Core.
The script interpreter is now gated behind the `broken_consensus_code` flag
for this reason.
Given the complexity of both C++ and Rust, it is unlikely that this will Given the complexity of both C++ and Rust, it is unlikely that this will
ever be fixed, and there are no plans to do so. Of course, patches to ever be fixed, and there are no plans to do so. Of course, patches to
fix specific consensus incompatibilities are welcome. fix specific consensus incompatibilities are welcome.