Get desktop application:
View/edit binary Protocol Buffers messages
Used in: , , ,
Must be [0.0, 1.0)
Specifies the currency type promised but does not imply issuing authority for the currency. That will depend on mint (group) keys.
ISO Currency Codes (ISO 4217:2015) plus arbitrary codes.
Used in:
Used in:
Used in:
0th signature must be signed by a mint credential and uses recoverable ecdsa NistP256. All other signatures must be signed by a TTC credential. For all non-base signatures, the first bytes are the serialized credential. Trimming "reissues" the History and adds the trimmed_from tag. Trim servers use a different keypair than the mint which enables easier discovery of trim key abuse. The risk is still high, so other approaches may be appealing -- token swapping or having every trim server act as the "first" minted credential such that they can double spend but never change the value or original token tags.
Used in: , , , , ,
Signature over a serialized ticket with a recovery byte appended.
Used in: ,
epoch timestamp; only honored in first transfer.
original transfer signature (only verifiable by authority)
new value which is less than the Descriptor value
Used in:
Used in:
Initially, a number in the range [0, 64).
# of epochs (currently 86400 second periods) it is valid.
currrent epoch value and the required ticket request signature basename.
Used in: , , , , , , ,
TODO: optional "hint" value for splits?
Used in:
Credential commitment with policy.
This is only populated during signing or verification, not for transport.
Or digest(descriptor) for the 0th.
Used in: