Expand description
Core data structures for the Blockle blockchain.
Everything consensus-serializable lives here: block headers, blocks,
transactions (including the reserved shielded bundle), amounts, keys and
bech32m block1… addresses, Merkle roots, and the canonical binary
encoding used for hashing and signing.
Re-exports§
pub use amount::format_amount;pub use amount::parse_amount;pub use amount::COIN;pub use auxpow::AuxPow;pub use block::Block;pub use block::BlockHeader;pub use hash::blake2b_256;pub use hash::display_hash;pub use hash::sha256d;pub use hash::Hash32;pub use keys::decode_address;pub use keys::encode_address;pub use keys::Address;pub use keys::Keypair;pub use transaction::ContractAction;pub use transaction::OutPoint;pub use transaction::ShieldedBundle;pub use transaction::ShieldedOutput;pub use transaction::ShieldedSpend;pub use transaction::ShieldedTransfer;pub use transaction::Transaction;pub use transaction::TxInput;pub use transaction::TxOutput;
Modules§
- amount
- BLOCK amounts. The base unit is 1e-8 BLOCK (like a satoshi).
- auxpow
- Merged-mining (AuxPoW) primitives.
- block
- Block and block header.
- encode
- Canonical binary encoding for consensus hashing and signing.
- hash
- Hashing helpers.
- keys
- Post-quantum keys and addresses.
- merkle
- Merkle root over transaction ids (Blake2b-256, Bitcoin-style pairing: odd levels duplicate the last node).
- transaction
- Blockle’s transaction model: a note/output system (UTXO-style) with a reserved shielded bundle so the privacy milestone extends the same wire format instead of forking it.