rust-bitcoin

taproot-primitives: Fix hex width specifier

This is printing a `u8`, because we are using alternate (includes
`0x`) the width specifier should be 4 not 2. Found by clippy but
debugged by Poelstra.

Add test for LeafVersion formatting change

We just patch the `Display` impl for `LeafVersion::Future`. Add a test
that if move before the last patch fails, proving the last patch was
indeed a bug fix.

Fix ArrayVec::try_push Doc comment

Correct the Doc comment to rightly reference `CapacityExceeded` instead
of `CAPSizeExceeded`.

consensus_encoding: Release stable 1.0.0

In preparation for releasing `v1.0.0` add a changelog, bump the
version, update all downstream crates, and update the lockfiles.

consensus_enocding: Update the readme

In preparation for the 1.0 release remove mention of the RC release
process and make an effort to document how we got from the old
consensus encoding code to this crate.

p2p: change CommandString to wrap 12 byte array instead of Cow

Bitcoin P2P Command strings are always 12-byte ASCII, therefore the
underlying data type can be represented as a fixed 12 byte array. This
removes the need for any type of dynamic allocations using COW.

The `CommandString` invariant that the input must not be longer than 12
bytes and must be ASCII is enforced in all possible construction
avenues. As such, both `try_from_stringly()` and the `end()` method in
the decoder enforce the invariant.

p2p: mark CommandString as Copy

p2p: group struct and impl for V1NetworkMessage

consensus_encoding: Adjust docs spelling and grammar

consensus_encoding: run formatter

consensus_encoding: switch tests to should_panic macro

hashes: Update API files

hashes: Remove Bytes and LEN from HashEngine

Simplify the API by removing Bytes and LEN from HashEngine.
Callers can still use HashEngine::Hash::LEN and
HashEngine::Hash::Bytes to access those values.

This will automatically solve the inconsistency between
HashEngine and Hash we found for sha512_256 output size.

Use check_encode in consensus comparison fuzz target

The consensus encoding comparison fuzz target compares old encodings
to new encodings between master and bitcoin 0.32. Presently, it does
so by allocating a vector for the old serialisation and the new.
The new check_encode function in consensus_encoding can instead be used
to eliminate a Vec allocation and directly compare the encoder output
of the new encoding against the encoded vector of the old encoding.

Replace encode_to_vec and assert_eq! call with use of the check_encode
function.

Update API

consensus_encoding: add checked decode functions for tests

Adjust docs for Header import

p2p: Change CommandStringDecoder to newtype decoder

The CommandStringDecoder is a newtype-style decoder, implemented as a
complete struct with an inner field. This can trivially be converted to
a newtype struct and thus defined using the decoder_newtype macro.

Change CommandStringDecoder to follow the tuple struct format.
Change CommandStringDecoder definition to use decoder_newtype macro.

p2p: Replace decoder definitions with decoder_newtype macro

Introduce decoder_newtype macro in p2p through the include! macro.
Replace most newtype Decoder structs in p2p with decoder_newtype calls.

Move PushBytes and co to primitives

To simplify the move of Address to the new addresses crate, the
PushBytes type can be moved to primitives first.

Move PushBytes, PushBytesBuf, PushBytesError and PushBytesErrorReport
to primitives.

primitives: Add tests to cover PushBytes types

Having moved to primitives, the tests must cover all mutants in
PushBytes. Since existing tests from bitcoin all rely on extension
traits or other functionality, new tests should be created just for
PushBytes and PushBytesBuf.

Update API files

Fix lint errors in primitives and crypto

With the move of PushBytes and co to primitives, a handful of lint
errors are now thrown in both crypto and primitives.

Fix lint errors in primitives and crypto.

Move impl_asref_push_bytes macro to include

This macro will be used in multiple crates following the move of
PushBytes to primitives. To reduce code duplication, it should be
moved to the include directory and introduced into each crate as
needed using include!.

Move impl_asref_push_bytes to include/asref_pushbytes.rs and include!
in bitcoin.

crypto: Add primitives dep

In order to stabilise PushBytes now, the impls of AsRef/Borrow, etc
between PushBytes and the crypto types need to be in a non-stable
crate until the crypto types are stable. While we want primitives to
depend on crypto eventually, for now, the only way to stabilise
PushBytes in primitives is to invert the dependency and put the impls
in crypto.