Module tuxedo_core::types

The common types that will be used across a Tuxedo runtime, and not specific to any one piece

Structs

• Input
  A reference the a utxo that will be consumed along with proof that it may be consumed
• Output
  An opaque piece of Transaction output data. This is how the data appears at the Runtime level. After the verifier is checked, strongly typed data will be extracted and passed to the constraint checker. In a cryptocurrency, the data represents a single coin. In Tuxedo, the type of the contained data is generic.
• OutputRef
  A reference to a output that is expected to exist in the state.
• Transaction
  A UTXO Transaction

Enums

• RedemptionStrategy
  An input can be consumed in two way. It can be redeemed normally (probably with some signature, or proof) or it can be evicted. This enum is isomorphic to Option<Vec<u8>> but has more meaningful names.
• UtxoError

Type Aliases

• Block
  An alias for a Tuxedo block with all the common parts filled in.
• BlockNumber
  All Tuxedo chains use the same u32 BlockNumber.
• DispatchResult
  The Result of dispatching a UTXO transaction.
• Hash
• Header
  Because all tuxedo chains use the same Blocknumber and Hash types, they also use the same concrete header type.
• OpaqueBlock
  Opaque block type. It has a Standard Tuxedo header, and opaque transactions.
• OpaqueHash
  Opaque block hash type.