Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
, ,Used in:
Used in:
Used in:
,BlockExecutionData represents the collection of data produced while execiting the block.
Used in:
,Block ID of the block that was executed.
Ordered list of ChunkExecutionData produced while executing the block. Note: there will be one ChunkExecutionData per collection in the block, plus one for the service chunk. The service chunk is executed last and is always the last chunk in the list.
Used in:
, , ,deprecated!! value will be empty. replaced by parent_vote_indices
Used in:
Used in:
, , , , , , , , , ,Used in:
state when starting executing this chunk
Events generated by executing results
Block id of the execution result this chunk belongs to
total amount of computation used by running all txs in this chunk
number of transactions inside the collection
chunk index inside the ER (starts from zero)
EndState inferred from next chunk or from the ER
a commitment over sorted list of register changes
ChunkExecutionData represents the collection of data produced while executing a chunk.
Used in:
Ordered list of transactions included in the collection that was executed in the chunk.
Events emitted by transactions in the collection. Note: events listed in the last ChunkExecutionData in the BlockExecutionData were emitted by the service transaction. Some, but not all, of these events are service events.
TrieUpdate produced by executing the collection. TrieUpdates contain a list of registers that were modified during chunk execution. The value included is the new value of the register.
Transaction results produced by executing the collection. Note: these are not the same type of results returned by other RPCs. These results are sepcific to execution data. The most notable difference is they only include a boolean value to indicate whether or not an error was encountered during execution, not the error itself.
Used in:
Used in:
deprecated!! value will be empty. replaced by signer_indices
Used in:
, , , , ,Used in:
, , , , , , , , , , ,ExecutionDataCollection represents the collection of transactions that were executed within a chunk. Note: this is not the same type as the entities.Collection.
Used in:
List of transactions included in the collection.
ExecutionDataTransactionResult represents the result of executing a transaction.
Used in:
Transaction ID of the transaction that was executed.
Boolean indicating whether or not the transaction's execution failed with an error.
Amount of computation used during execution.
Used in:
Used in:
, ,KeyPart represents a part of a register key.
Used in:
Type of the key part.
Value of the key part.
Used in:
, , , , , , , , , , , , , ,Used in:
The currently running node software version.
The git commit hash of the currently running node software.
The unique identifier for the node's network within the current spork.
The protocol version of the currently running node software.
The spork root block height. This is the height of the first sealed block in the spork network.
The node's root block height. This is the first sealed block in the node's protocol database. If the node started at the beginning of the spork, it is the same as the spork root block height. If the node started after the beginning of the spork, it is the height of the first sealed block indexed.
Payload represents the key-value pair of a register.
Used in:
List of key parts that make up the register key. Can be converted into register id.
Value of the register.
Used in:
Used in:
Used in:
Used in:
Used in:
, , , ,Used in:
Used in:
Used in:
,TrieUpdate produced by executing the collection. TrieUpdates contain a list of registers that were modified during chunk execution. The value included is the new value of the register.
Used in:
RootHash is the root hash of the trie before the update is applied.
List of register paths updated. Note: paths and payloads map 1:1 with eachother. i.e. for each element in path, the value in payloads at the same index is the value of the register at that path.
List of register values updated. Note: paths and payloads map 1:1 with eachother. i.e. for each element in path, the value in payloads at the same index is the value of the register at that path.