Anchor identifier - a commitment to the anchor data.
Unique data attachment identifier
Blinding factor used in creating Pedersen commitment to an [AtomicValue].
Unique state transition bundle identifier equivalent to the bundle
commitment hash
Confidential version of an attachment information.
Confidential version of an structured state data.
Confidential version of the additive state.
Contract history accumulates raw data from the contract history, extracted
from a series of consignments over the time. It does consensus ordering of
the state data, but it doesn’t interpret or validates the state against the
schema.
Unique contract identifier equivalent to the contract genesis commitment
Contract state provides API to read consensus-valid data from the
ContractHistory.
Fast-forward version code
value provided for a blinding factor overflows prime field order for
Secp256k1 curve.
A dumb placeholder for a future bulletproofs.
Unique operation (genesis, extensions & state transition) identifier
equivalent to the commitment hash
RGB contract operation output pointer, defined by the operation ID and
output number.
Reserved byte.
State item for a homomorphically-encryptable state.
Schema identifier.
Blind version of transaction outpoint-based single-use-seal
Struct using for storing Void (i.e. absent) state
Txid and height information ordered according to the RGB consensus rules.
State data are assigned to a seal definition, which means that they are
owned by a person controlling spending of the seal UTXO, unless the seal
is closed, indicating that a transfer of ownership had taken place
Errors parsing string representation of a blinding factor.
An atom of an additive state, which thus can be monomorphically encrypted.
Today we support only a single format of confidential data, because of the
limitations of the underlying secp256k1-zkp library: it works only with
u64 numbers. Nevertheless, homomorphic commitments can be created to
everything that has up to 256 bits and commutative arithmetics, so in the
future we plan to support more types. We reserve this possibility by
internally encoding [ConfidentialFormat] with the same type specification
details as used for [DateFormat]
Aggregated type used to supply full contract operation type and
transition/state extension type information
Node type: genesis, extensions and state transitions
Seal outpoint is not a seal definition. It is an accessory structure
allowing to
Range proof value.
Errors verifying range proofs.
Virtual machine and machine-specific script data.
Categories of the state
Categories of the state
Virtual machine types.
RGB consensus information about the current mined height of a witness
transaction defining the ordering of the contract state data.