CashAssembly Template) specifies a set
of locking scripts, unlocking scripts, and other information required to use
a certain authentication scheme. Templates fully describe wallets and
protocols in a way that can be shared between software clients.
The URI that identifies the JSON Schema used by this template. Try:
to enable documentation, autocompletion, and validation in JSON documents.
An optionally multi-line, free-form, human-readable description for this authentication template (for use in user interfaces). If displayed, this description should use a monospace font to properly render ASCII diagrams.
A map of entities defined in this authentication template.
Object keys are used as entity identifiers, and by convention, should use
A single-line, Title Case, human-readable name for this authentication template (for use in user interfaces).
A scenario describes a context in which one or more scripts might be used. Scenarios are used for transaction estimation and as an integrated testing system for authentication templates.
Object keys are used as scenario identifiers, and by convention, should use
A map of scripts used in this authentication template.
Object keys are used as script identifiers, and by convention, should use
A list of authentication virtual machine versions supported by this template.
Virtual machine identifiers use the format
the currency code used to identify the network, and
YYYY_MM is the year
and month in which the specified VM version became active on the indicated
Identifiers with the
_SPEC suffix indicate that this template is intended
for compatibility with a future virtual machine version, but at the time
the template was created, that virtual machine had not yet become active on
the specified chain.
A number identifying the format of this AuthenticationTemplate.
Currently, this implementation requires
version be set to
Generated using TypeDoc