zebra/zebra-chain/src/lib.rs

//! Blockchain-related datastructures for Zebra. 🦓
#![deny(missing_docs)]

#[macro_use]
extern crate failure;

pub mod block;
pub mod types;
pub mod serialization;
WIP: Version message and various sub structures Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> 2019-09-10 13:27:10 -07:00			`//! Blockchain-related datastructures for Zebra. 🦓`
			`#![deny(missing_docs)]`

Move serialization to zebra-chain, rework traits. The core serialization logic is now in zebra-chain and consists of two pairs of traits: These are analogues of the Serde `Serialize` and `Deserialize` traits, but explicitly intended for consensus-critical serialization formats. Thus some struct `Foo` may have derived `Serialize` and `Deserialize` implementations for (internal) use with Serde, and explicitly-written `ZcashSerialize` and `ZcashDeserialize` implementations for use in consensus-critical contexts. The consensus-critical implementations provide `zcash`-prefixed `zcash_serialize` and `zcash_deserialize` methods to make it clear in client contexts that the serialization is consensus-critical. These are utility traits, analogous to the `ReadBytesExt` and `WriteBytesExt` traits provided by `byteorder`. A generic implementation is provided for any `io::Read` or `io::Write`, so that bringing the traits into scope adds additional Zcash-specific traits to generic readers and writers -- for instance, writing a `u64` in the Bitcoin "CompactSize" format. 2019-09-15 06:37:16 -07:00			`#[macro_use]`
			`extern crate failure;`

WIP: Version message and various sub structures Co-authored-by: Henry de Valence <hdevalence@hdevalence.ca> 2019-09-10 13:27:10 -07:00			`pub mod block;`
			`pub mod types;`
Move serialization to zebra-chain, rework traits. The core serialization logic is now in zebra-chain and consists of two pairs of traits: These are analogues of the Serde `Serialize` and `Deserialize` traits, but explicitly intended for consensus-critical serialization formats. Thus some struct `Foo` may have derived `Serialize` and `Deserialize` implementations for (internal) use with Serde, and explicitly-written `ZcashSerialize` and `ZcashDeserialize` implementations for use in consensus-critical contexts. The consensus-critical implementations provide `zcash`-prefixed `zcash_serialize` and `zcash_deserialize` methods to make it clear in client contexts that the serialization is consensus-critical. These are utility traits, analogous to the `ReadBytesExt` and `WriteBytesExt` traits provided by `byteorder`. A generic implementation is provided for any `io::Read` or `io::Write`, so that bringing the traits into scope adds additional Zcash-specific traits to generic readers and writers -- for instance, writing a `u64` in the Bitcoin "CompactSize" format. 2019-09-15 06:37:16 -07:00			`pub mod serialization;`