Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
A human readable name identifying the Agent
Unix UTC timestamp of approximately when this agent was registered
Used in:
The natural key of the Record
The public key of the Agent to whom the proposal is sent
The role being proposed (owner, custodian, or reporter)
The respose to the Proposal (accept, reject, or cancel)
Used in:
Used in:
The serialized version of the BatchHeader
The signature derived from signing the header
A list of the transactions that match the list of transaction_ids listed in the batch header
A debugging flag which indicates this batch should be traced through the system, resulting in a higher level of debugging output.
Public key for the client that signed the BatchHeader
List of transaction.header_signatures that match the order of transactions required for the batch
Used in:
The human-readable name of the Agent. This does not need to be unique.
Used in:
The natural key of the Record
the public key of the Agent to whom the Proposal is sent (must be different from the Agent creating the Proposal)
Used in:
The natural key of the Record
The name of the RecordType this Record belongs to
Used in:
Used in:
The natural key of the Record
Used in: ,
Coordinates are expected to be in millionths of a degree
Used in:
The name of the Property, e.g. "temperature". This must be unique among Properties.
The natural key of the Property's associated Record.
The Property's type (int, string, etc.)
The Reporters authorized to send updates, sorted by index. New Reporters should be given an index equal to the number of Reporters already authorized.
The page to which new updates are added. This number represents the last 4 hex characters of the page's address. Consequently, it should not exceed 16^4 = 65536.
A flag indicating whether the first 16^4 pages have been filled. This is used to calculate the last four hex characters of the address of the page containing the earliest updates. When it is false, the earliest page's address will end in "0001". When it is true, the earliest page's address will be one more than the current_page, or "0001" if the current_page is "ffff".
If set to true, values may only be set for this Property during Record creation, not later with updates.
Used with numbers to communicate how the integer value should be converted to a fractional number. Uses the same principle as scientific notation. A number value of 1, with an exponent of 3, would be 1,000 (1 * 10^3). A number value of 1, with an exponent of -3, would be 0.001 (1 * 10^-3).
Used with ENUM data types, the string names of available options
Used with STRUCT data types, defines the properties a struct must contain
This optional metadata describes the unit a Property is measured in
Used in:
The public key of the Agent authorized to report updates.
An update must be stored with some way of identifying which Agent sent it. Storing a full public key for each update would be wasteful, so instead Reporters are identified by their index in the `reporters` field.
Used in:
The name of the page's associated Property and the record_id of its associated Record. These are required to distinguish pages with colliding addresses.
ReportedValues are sorted first by timestamp, then by reporter_index
Used in:
The index of the reporter id in reporters field
Approximately when this value was reported, as a Unix UTC timestamp
The type-specific value of the update. Only one of these fields should be used, and it should match the type specified for this Property in the RecordType.
Used in: , ,
The name of the property, e.g. "temperature"
The Property's type (int, string, etc.)
A flag indicating whether initial values must be provided for the Property when a Record is created.
Another flag. If set to true, values may only be set for this Property during Record creation, not later with updates.
A flag that indicates a property may not be set at record creation, only later during subsequent property updates.
Used with numbers to communicate how the integer value should be converted to a fractional number. Uses the same principle as scientific notation. A number value of 1, with an exponent of 3, would be 1,000 (1 * 10^3). A number value of 1, with an exponent of -3, would be 0.001 (1 * 10^-3).
Used with ENUM data types, the string names of available options
Used with STRUCT data types, defines the properties a struct must contain
This optional metadata describes the unit a Property is measured in
Used in: , ,
Used in: , ,
The name of the property being set
The PropertyValue's type (int, string, etc.)
The type-specific value to initialize or update a Property. Only one of these fields should be used, and it should match the type specified for this Property in the RecordType.
Used in:
The time at which the Proposal was created
The public key of the Agent sending the Proposal. This Agent must be the owner of the Record (or the custodian, if the Proposal is to transfer custodianship).
The public key of the Agent to whom the Proposal is sent.
What the Proposal is for -- transferring ownership, transferring custodianship, or authorizing a reporter.
The names of properties for which the reporter is being authorized (empty for owner or custodian transfers)
The status of the Proposal. For a given Record and receiving Agent, there can be only one open Proposal at a time for each role.
The human-readable terms of transfer.
Used in: , ,
Used in:
Used in:
The user-defined natural key which identifies the object in the real world (for example a serial number)
Ordered oldest to newest by timestamp
Flag indicating whether the Record can be updated. If it is set to true, then the record has been finalized and no further changes can be made to it or its Properties.
Used in:
Used in:
A unique human-readable designation for the RecordType
Used in:
The natural key of the Record
The reporter's public key
The names of the Properties for which the reporter's authorization is revoked
Approximately when transaction was submitted, as a Unix UTC timestamp
The transaction handler will read from just one of these fields according to the Action.
Used in:
Used in: ,
The serialized version of the TransactionHeader
The signature derived from signing the header
The payload is the encoded family specific information of the transaction. Example cbor({'Verb': verb, 'Name': name,'Value': value})
Public key for the client who added this transaction to a batch
A list of transaction signatures that describe the transactions that must be processed before this transaction can be valid
The family name correlates to the transaction processor's family name that this transaction can be processed on, for example 'intkey'
The family version correlates to the transaction processor's family version that this transaction can be processed on, for example "1.0"
A list of addresses that are given to the context manager and control what addresses the transaction processor is allowed to read from.
A random string that provides uniqueness for transactions with otherwise identical fields.
A list of addresses that are given to the context manager and control what addresses the transaction processor is allowed to write to.
The sha512 hash of the encoded payload
Public key for the client that signed the TransactionHeader
A simple list of transactions that needs to be serialized before it can be transmitted to a batcher.
Used in:
The natural key of the Record