package types

Get desktop application:
View/edit binary Protocol Buffers messages

Used in: Event, GetEventsByEventAccessPathRequest, WriteOp

• bytes address = 1

• bytes path = 2

Account state as a whole. After execution, updates to accounts are passed in this form to storage for persistence.

Used in: TransactionToCommit

• bytes address = 1

  Account address

• bytes blob = 2

  Account state blob

Used in: AccountStateWithProof

• bytes blob = 1

The complete proof used to authenticate an account state.

Used in: AccountStateWithProof

• optional AccumulatorProof ledger_info_to_transaction_info_proof = 1

• optional TransactionInfo transaction_info = 2

• optional SparseMerkleProof transaction_info_to_account_proof = 3

Used in: GetAccountStateResponse, GetAccountTransactionBySequenceNumberResponse, GetEventsByEventAccessPathResponse

• uint64 version = 1

• optional AccountStateBlob blob = 2

• optional AccountStateProof proof = 3

Used in: AccountStateProof, EventProof, SignedTransactionProof, TransactionListWithProof

• uint64 bitmap = 1

  The bitmap indicating which siblings are default. 1 means non-default and 0 means default. The LSB corresponds to the sibling at the bottom of the accumulator. The leftmost 1-bit corresponds to the sibling at the level just below root level in the accumulator, since this one is always non-default.

• repeated bytes non_default_siblings = 2

  The non-default siblings. The ones near the root are at the beginning of the list.

Used in: ExecutionStatus

• ArithmeticError.ArithmeticErrorType error_code = 1

Used in: ArithmeticError

• UnknownArithmeticError = 0

• Underflow = 1

• Overflow = 2

• DivisionByZero = 3

  Fill with more later

user-defined assertion error code number

Used in: ExecutionStatus

• uint64 assertion_error_code = 1

Errors that can arise from binary decoding (deserialization)

Used in: VMStatus

• UnknownBinaryError = 0

• Malformed = 1

• BadMagic = 2

• UnknownVersion = 3

• UnknownTableType = 4

• UnknownSignatureType = 5

• UnknownSerializedType = 6

• UnknownOpcode = 7

• BadHeaderTable = 8

• UnexpectedSignatureType = 9

• DuplicateTable = 10

Used in: ExecutionStatus

• DynamicReferenceError.DynamicReferenceErrorType error_code = 1

Used in: DynamicReferenceError

• UnknownDynamicReferenceError = 0

• MoveOfBorrowedResource = 1

• GlobalRefAlreadyReleased = 2

• MissingReleaseRef = 3

• GlobalAlreadyBorrowed = 4

  Fill with with more later

An event emitted from a smart contract

Used in: EventWithProof, EventsList, TransactionToCommit

• optional AccessPath access_path = 1

• uint64 sequence_number = 2

• bytes event_data = 3

The complete proof used to authenticate an event.

Used in: EventWithProof

• optional AccumulatorProof ledger_info_to_transaction_info_proof = 1

• optional TransactionInfo transaction_info = 2

• optional AccumulatorProof transaction_info_to_event_proof = 3

An event along with the proof for the event

Used in: GetEventsByEventAccessPathResponse, ValidatorChangeEventWithProof

• uint64 transaction_version = 1

• uint64 event_index = 2

• optional Event event = 3

• optional EventProof proof = 4

A list of EventList's, each representing all events for a transaction.

Used in: TransactionListWithProof

• repeated EventsList events_for_version = 1

A list of events.

Used in: EventsForVersions, SignedTransactionWithProof

• repeated Event events = 1

Used in: VMStatus

• oneof execution_status

  • RuntimeStatus runtime_status = 1

  • AssertionFailure assertion_failure = 2

  • ArithmeticError arithmetic_error = 3

  • DynamicReferenceError reference_error = 4

Gets latest state for an account.

Used in: RequestItem

• bytes address = 1

  Account for which we are fetching the state.

State information returned by a get account state query.

Used in: ResponseItem

• optional AccountStateWithProof account_state_with_proof = 1

  Blob value representing the account state together with proof the client can utilize to verify it.

----------------------------------------------------------------------------- ---------------- Get single transaction by account + sequence number ----------------------------------------------------------------------------- Get transactions that altered an account - this includes both sent and received. A user of this should check that the data returned matches what they expect. As an example, a potential attack vector would be something like the following: Alice is buying an apple from Bob. Alice's phone signs a transaction X with sequence number N that pays coins to Bob. Alice transmits this signature to Bob's payment terminal which then submits the transaction and checks its status to see if Alice can be given the apple. However, as Bob is doing this Alice constructs a second transaction X' also with sequence number N. Alice gets that transaction inserted in the blockchain. If Bob isn't thoughtful about how he uses this API he may assume that if he asks for the N'th transaction on Alice's account that when the API returns that this means the transaction has gone through. The point here is that one should be careful in reading too much into "transaction X is on the chain" and focus on the logs, which tell you what the transaction did. If a client submitted a transaction, they should also verify that the hash of the returned transaction matches what they submitted. As an example, if a client has two wallets that share the same account, they may both submit a transaction at the same sequence number and only one will be committed. A client should never assume that if they receive the response that this transaction was included that it means that this is definitely the transaction that was submitted. They should check that the hash matches what they sent

Used in: RequestItem

• bytes account = 1

  Account for which to query transactions

• uint64 sequence_number = 2

• bool fetch_events = 3

  Set to true to fetch events for the transaction at this version

Transaction information for transactions requested by GetAccountTransactionsRequest

Used in: ResponseItem

• optional SignedTransactionWithProof signed_transaction_with_proof = 2

  When the transaction requested is committed, return the committed transaction with proof.

• optional AccountStateWithProof proof_of_current_sequence_number = 3

  When the transaction requested is not committed, we give a proof that shows the current sequence number is smaller than what would have been if the transaction was committed.

Get events that exist on an event access path. In the current world, a user may specify events that were received, events that were sent, or any event that modifies their account

Used in: RequestItem

• optional AccessPath access_path = 1

• uint64 start_event_seq_num = 2

  The sequence number of the event to start with for this query. Use a sequence number of MAX_INT to represent the latest.

• bool ascending = 3

  If ascending is true this query will return up to `limit` events that were emitted after `start_event_seq_num`. Otherwise it will return up to `limit` events before the offset. Both cases are inclusive.

• uint64 limit = 4

  Limit number of results

Used in: ResponseItem

• repeated EventWithProof events_with_proof = 1

  Returns an event and proof of each of the events in the request. The first element of proofs will be the closest to `start_event_seq_num`.

• optional AccountStateWithProof proof_of_latest_event = 2

  If the number of events returned is less than `limit` for an ascending query or if start_event_seq_num > the latest seq_num for a descending query, returns the state of the account containing the given access path in the latest state. This allows the client to verify that there are in fact no extra events. The LedgerInfoWithSignatures which is on the main UpdateToLatestLedgerResponse can be used to validate this.

Get up to limit transactions starting from start_version.

Used in: RequestItem

• uint64 start_version = 1

  The version of the transaction to start with for this query. Use a version of MAX_INT to represent the latest.

• uint64 limit = 2

  Limit number of results

• bool fetch_events = 3

  Set to true to fetch events for the transaction at each version

Used in: ResponseItem

• optional TransactionListWithProof txn_list_with_proof = 1

/ Even though we don't always need all hashes, we pass them in and return them / always so that we keep them in sync on the client and don't make the client / worry about which one(s) to pass in which cases / / This structure serves a dual purpose. / / First, if this structure is signed by 2f+1 validators it signifies the state / of the ledger at version `version` -- it contains the transaction / accumulator at that version which commits to all historical transactions. / This structure may be expanded to include other information that is derived / from that accumulator (e.g. the current time according to the time contract) / to reduce the number of proofs a client must get. / / Second, the structure contains a `consensus_data_hash` value. This is the / hash of an internal data structure that represents a block that is voted on / by consensus. / / Combining these two concepts when the consensus algorithm votes on a block B / it votes for a LedgerInfo with the `version` being the latest version that / will be committed if B gets 2f+1 votes. It sets `consensus_data_hash` to / represent B so that if those 2f+1 votes are gathered, the block is valid to / commit

Used in: LedgerInfoWithSignatures

• uint64 version = 1

  Current latest version of the system

• bytes transaction_accumulator_hash = 2

  Root hash of transaction accumulator at this version

• bytes consensus_data_hash = 3

  Hash of consensus-specific data that is opaque to all parts of the system other than consensus. This is needed to verify signatures because consensus signing includes this hash

• bytes consensus_block_id = 4

  The block id of the last committed block corresponding to this ledger info. This field is not particularly interesting to the clients, but can be used by the validators for synchronization.

• uint64 epoch_num = 5

  Epoch number corresponds to the set of validators that are active for this ledger info. The main motivation for keeping the epoch number in the LedgerInfo is to ensure that the client has enough information to verify that the signatures for this info are coming from the validators that indeed form a quorum. Without epoch number a potential attack could reuse the signatures from the validators in one epoch in order to sign the wrong info belonging to another epoch, in which these validators do not form a quorum. The very first epoch number is 0.

• uint64 timestamp_usecs = 6

  Timestamp that represents the microseconds since the epoch (unix time) that is generated by the proposer of the block. This is strictly increasing with every block. If a client reads a timestamp > the one they specified for transaction expiration time, they can be certain that their transaction will never be included in a block in the future (assuming that their transaction has not yet been included)

/ The validator node returns this structure which includes signatures / from each validator to confirm the state. The client needs to only pass / back the LedgerInfo element since the validator node doesn't need to know / the signatures again when the client performs a query, those are only there / for the client to be able to verify the state

Used in: UpdateToLatestLedgerResponse, ValidatorChangeEventWithProof

• repeated ValidatorSignature signatures = 1

  Signatures of the root node from each validator

• optional LedgerInfo ledger_info = 2

/ The unique identifier for a module on the chain.

Used in: VMVerificationStatus

• bytes address = 1

• string name = 2

The code for the transaction to execute

Used in: RawTransaction

• bytes code = 1

• repeated TransactionArgument arguments = 2

• repeated bytes modules = 3

A generic structure that describes a transaction that a client submits

• bytes sender_account = 1

  Sender's account address

• uint64 sequence_number = 2

  Sequence number of this transaction corresponding to sender's account.

• oneof payload

  • Program program = 3

    The transaction script to execute.

  • WriteSet write_set = 4

    A write set, used for genesis blocks and other magic transactions. This bypasses the rules for regular transactions so will typically be rejected. Only under special circumstances will it be accepted.

• uint64 max_gas_amount = 5

  Maximal total gas specified by wallet to spend for this transaction.

• uint64 gas_unit_price = 6

  The price to be paid for each unit of gas.

• uint64 expiration_time = 7

  Expiration time for this transaction. If storage is queried and the time returned is greater than or equal to this time and this transaction has not been included, you can be certain that it will never be included. If set to 0, there will be no expiration time

Used in: UpdateToLatestLedgerRequest

• oneof requested_items

  • GetAccountStateRequest get_account_state_request = 1

  • GetAccountTransactionBySequenceNumberRequest get_account_transaction_by_sequence_number_request = 2

  • GetEventsByEventAccessPathRequest get_events_by_event_access_path_request = 3

  • GetTransactionsRequest get_transactions_request = 4

Individual response items to the queries posed by the requests

Used in: UpdateToLatestLedgerResponse

• oneof response_items

  • GetAccountStateResponse get_account_state_response = 3

  • GetAccountTransactionBySequenceNumberResponse get_account_transaction_by_sequence_number_response = 4

  • GetEventsByEventAccessPathResponse get_events_by_event_access_path_response = 5

  • GetTransactionsResponse get_transactions_response = 6

Used in: ExecutionStatus

• UnknownRuntimeStatus = 0

• Executed = 1

• OutOfGas = 2

• ResourceDoesNotExist = 3

  We tried to access a resource that does not exist under the account.

• ResourceAlreadyExists = 4

  We tried to create a resource under an account where that resource already exists.

• EvictedAccountAccess = 5

  We accessed an account that is evicted.

• AccountAddressAlreadyExists = 6

  We tried to create an account at an address where an account already exists.

• TypeError = 7

• MissingData = 8

• DataFormatError = 9

• InvalidData = 10

• RemoteDataError = 11

• CannotWriteExistingResource = 12

• ValueSerializationError = 13

• ValueDeserializationError = 14

• DuplicateModuleName = 15

  The sender is trying to publish a module named `M`, but the sender's account already contains a module with this name.

A generic structure that represents signed RawTransaction

Used in: admission_control.SubmitTransactionRequest, mempool.AddTransactionWithValidationRequest, SignedTransactionWithProof, SignedTransactionsBlock, TransactionListWithProof, TransactionToCommit

• bytes raw_txn_bytes = 1

  The serialized Protobuf bytes for RawTransaction, for which the signature was signed. Protobuf doesn't guarantee the serialized bytes is canonical across different language implementations, but for our use cases for transaction it is not necessary because the client is the only one to produce this bytes, which is then persisted in storage.

• bytes sender_public_key = 2

  public key that corresponds to RawTransaction::sender_account

• bytes sender_signature = 3

  signature for the hash

The complete proof used to authenticate a signed transaction.

Used in: SignedTransactionWithProof

• optional AccumulatorProof ledger_info_to_transaction_info_proof = 1

• optional TransactionInfo transaction_info = 2

Used in: GetAccountTransactionBySequenceNumberResponse

• uint64 version = 1

  The version of the returned signed transaction.

• optional SignedTransaction signed_transaction = 2

  The transaction itself.

• optional SignedTransactionProof proof = 3

  The proof authenticating the signed transaction.

• optional EventsList events = 4

  The events yielded by executing the transaction, if requested.

A generic structure that represents a block of transactions originated from a particular validator instance.

Used in: mempool.GetBlockResponse

• repeated SignedTransaction transactions = 1

  Set of Signed Transactions

• bytes validator_public_key = 2

  Public key of the validator that created this block

• bytes validator_signature = 3

  Signature of the validator that created this block

Used in: AccountStateProof

• bytes leaf = 1

  This proof can be used to authenticate whether a given leaf exists in the tree or not. In Rust: - If this is `Some(HashValue, HashValue)` - If the first `HashValue` equals requested key, this is an inclusion proof and the second `HashValue` equals the hash of the corresponding account blob. - Otherwise this is a non-inclusion proof. The first `HashValue` is the only key that exists in the subtree and the second `HashValue` equals the hash of the corresponding account blob. - If this is `None`, this is also a non-inclusion proof which indicates the subtree is empty. In protobuf, this leaf field should either be - empty, which corresponds to None in the Rust structure. - exactly 64 bytes, which corresponds to Some<(HashValue, HashValue)> in the Rust structure.

• bytes bitmap = 2

  The bitmap indicating which siblings are default. 1 means non-default and 0 means default. The MSB of the first byte corresponds to the sibling at the top of the Sparse Merkle Tree. The rightmost 1-bit of the last byte corresponds to the sibling at the bottom, since this one is always non-default.

• repeated bytes non_default_siblings = 3

  The non-default siblings. The ones near the root are at the beginning of the list.

An argument to the transaction if the transaction takes arguments

Used in: Program

• TransactionArgument.ArgType type = 1

• bytes data = 2

Used in: TransactionArgument

• U64 = 0

• ADDRESS = 1

• STRING = 2

• BYTEARRAY = 3

`TransactionInfo` is the object we store in the transaction accumulator. It consists of the transaction as well as the execution result of this transaction. This are later returned to the client so that a client can validate the tree

Used in: AccountStateProof, EventProof, SignedTransactionProof, TransactionListWithProof

• bytes signed_transaction_hash = 1

  Hash of the signed transaction that is stored

• bytes state_root_hash = 2

  The root hash of Sparse Merkle Tree describing the world state at the end of this transaction

• bytes event_root_hash = 3

  The root hash of Merkle Accumulator storing all events emitted during this transaction.

• uint64 gas_used = 4

  The amount of gas used by this transaction.

A list of consecutive transactions with proof. This is mainly used for state synchronization when a validator would request a list of transactions from a peer, verify the proof, execute the transactions and persist them. Note that the transactions are supposed to belong to the same epoch E, otherwise verification will fail.

Used in: GetTransactionsResponse

• repeated SignedTransaction transactions = 1

  The list of transactions.

• repeated TransactionInfo infos = 2

  The list of corresponding TransactionInfo objects.

• optional EventsForVersions events_for_versions = 3

  The list of corresponding Event objects (only present if fetch_events was set to true in req)

• optional google.protobuf.UInt64Value first_transaction_version = 4

  If the list is not empty, the version of the first transaction.

• optional AccumulatorProof proof_of_first_transaction = 5

  The proofs of the first and last transaction in this chunk. When this is used for state synchronization, the validator who requests the transactions will provide a version in the request and the proofs will be relative to the given version. When this is returned in GetTransactionsResponse, the proofs will be relative to the ledger info returned in UpdateToLatestLedgerResponse.

• optional AccumulatorProof proof_of_last_transaction = 6

Transaction struct to commit to storage

• optional SignedTransaction signed_txn = 1

  The signed transaction which was executed

• repeated AccountState account_states = 2

  State db updates

• repeated Event events = 3

  Events yielded by the transaction.

• uint64 gas_used = 4

  The amount of gas used.

This API is used to update the client to the latest ledger version and optionally also request 1..n other pieces of data. This allows for batch queries. All queries return proofs that a client should check to validate the data. Note that if a client only wishes to update to the latest LedgerInfo and receive the proof that this latest ledger extends the client_known_version ledger the client had, they can simply set the requested_items to an empty list.

Used as request type in: admission_control.AdmissionControl.UpdateToLatestLedger

• uint64 client_known_version = 1

  This is the version the client already trusts. Usually the client should set this to the version it obtained the last time it synced with the chain. If this is the first time ever the client sends a request, it must use the waypoint hard-coded in its software.

• repeated RequestItem requested_items = 2

  The items for which we are requesting data in this API call.

Response from getting latest ledger

Used as response type in: admission_control.AdmissionControl.UpdateToLatestLedger

• repeated ResponseItem response_items = 1

  Responses to the queries posed by the requests. The proofs generated will be relative to the version of the latest ledger provided below.

• optional LedgerInfoWithSignatures ledger_info_with_sigs = 2

  The latest ledger info this node has. It will come with at least 2f+1 validator signatures as well as a proof that shows the latest ledger extends the old ledger the client had.

• repeated ValidatorChangeEventWithProof validator_change_events = 3

  Validator change events from what the client last knew. This is used to inform the client of validator changes from the client's last known version until the current version

These are errors that the VM might raise if a violation of internal invariants takes place.

Used in: VMStatus

• UnknownInvariantViolationError = 0

• OutOfBoundsIndex = 1

• OutOfBoundsRange = 2

• EmptyValueStack = 3

• EmptyCallStack = 4

• PCOverflow = 5

• LinkerError = 6

• LocalReferenceError = 7

• StorageError = 8

The status of the VM

Used in: admission_control.SubmitTransactionResponse

• oneof error_type

  • VMValidationStatus validation = 1

  • VMVerificationStatusList verification = 2

  • VMInvariantViolationError invariant_violation = 3

  • BinaryError deserialization = 4

  • ExecutionStatus execution = 5

Used in: VMStatus

• VMValidationStatusCode code = 1

• string message = 2

The status of a transaction as determined by the prologue.

Used in: VMValidationStatus

• UnknownValidationStatus = 0

  We don't want the default value to be valid

• InvalidSignature = 1

  The transaction has a bad signature

• InvalidAuthKey = 2

  Bad account authentication key

• SequenceNumberTooOld = 3

  Sequence number is too old

• SequenceNumberTooNew = 4

  Sequence number is too new

• InsufficientBalanceForTransactionFee = 5

  Insufficient balance to pay minimum transaction fee

• TransactionExpired = 6

  The transaction has expired

• SendingAccountDoesNotExist = 7

  The sending account does not exist

• RejectedWriteSet = 8

  This write set transaction was rejected because it did not meet the requirements for one.

• InvalidWriteSet = 9

  This write set transaction cannot be applied to the current state.

• ExceededMaxTransactionSize = 10

  Length of program field in raw transaction exceeded max length

• UnknownScript = 11

  This script is not on our whitelist of script.

• UnknownModule = 12

  Transaction is trying to publish a new module.

• MaxGasUnitsExceedsMaxGasUnitsBound = 13

  Max gas units submitted with transaction exceeds max gas units bound in VM

• MaxGasUnitsBelowMinTransactionGasUnits = 14

  Max gas units submitted with transaction not enough to cover the intrinsic cost of the transaction.

• GasUnitPriceBelowMinBound = 15

  Gas unit price submitted with transaction is below minimum gas price set in the VM.

• GasUnitPriceAboveMaxBound = 16

  Gas unit price submitted with the transaction is above the maximum gas price set in the VM.

When a code module/script is published it is verified. These are the possible errors that can arise from the verification process.

Used in: VMVerificationStatus

• UnknownVerificationError = 0

  Likewise default to a unknown verification error

• IndexOutOfBounds = 1

• RangeOutOfBounds = 2

• InvalidSignatureToken = 3

• InvalidFieldDefReference = 4

• RecursiveStructDefinition = 5

• InvalidResourceField = 6

• InvalidFallThrough = 7

• JoinFailure = 8

• NegativeStackSizeWithinBlock = 9

• UnbalancedStack = 10

• InvalidMainFunctionSignature = 11

• DuplicateElement = 12

• InvalidModuleHandle = 13

• UnimplementedHandle = 14

• InconsistentFields = 15

• UnusedFields = 16

• LookupFailed = 17

• VisibilityMismatch = 18

• TypeResolutionFailure = 19

• TypeMismatch = 20

• MissingDependency = 21

• PopReferenceError = 22

• PopResourceError = 23

• ReleaseRefTypeMismatchError = 24

• BrTypeMismatchError = 25

• AssertTypeMismatchError = 26

• StLocTypeMismatchError = 27

• StLocUnsafeToDestroyError = 28

• RetUnsafeToDestroyError = 29

• RetTypeMismatchError = 30

• FreezeRefTypeMismatchError = 31

• FreezeRefExistsMutableBorrowError = 32

• BorrowFieldTypeMismatchError = 33

• BorrowFieldBadFieldError = 34

• BorrowFieldExistsMutableBorrowError = 35

• CopyLocUnavailableError = 36

• CopyLocResourceError = 37

• CopyLocExistsBorrowError = 38

• MoveLocUnavailableError = 39

• MoveLocExistsBorrowError = 40

• BorrowLocReferenceError = 41

• BorrowLocUnavailableError = 42

• BorrowLocExistsBorrowError = 43

• CallTypeMismatchError = 44

• CallBorrowedMutableReferenceError = 45

• PackTypeMismatchError = 46

• UnpackTypeMismatchError = 47

• ReadRefTypeMismatchError = 48

• ReadRefResourceError = 49

• ReadRefExistsMutableBorrowError = 50

• WriteRefTypeMismatchError = 51

• WriteRefResourceError = 52

• WriteRefExistsBorrowError = 53

• WriteRefNoMutableReferenceError = 54

• IntegerOpTypeMismatchError = 55

• BooleanOpTypeMismatchError = 56

• EqualityOpTypeMismatchError = 57

• ExistsResourceTypeMismatchError = 58

• BorrowGlobalTypeMismatchError = 59

• BorrowGlobalNoResourceError = 60

• MoveFromTypeMismatchError = 61

• MoveFromNoResourceError = 62

• MoveToSenderTypeMismatchError = 63

• MoveToSenderNoResourceError = 64

• CreateAccountTypeMismatchError = 65

• ModuleAddressDoesNotMatchSender = 66

  The self address of a module the transaction is publishing is not the sender address

• NoModuleHandles = 67

  The module does not have any module handles. Each module or script must have at least one module handle.

Used in: VMVerificationStatusList

• VMVerificationStatus.StatusKind status_kind = 1

• uint32 module_idx = 2

  For StatusKind::SCRIPT and DEPENDENCY this is ignored.

• VMVerificationErrorKind error_kind = 3

• string message = 4

• optional ModuleId dependency_id = 5

  For StatusKind::SCRIPT and MODULE this is ignored.

Used in: VMVerificationStatus

• SCRIPT = 0

• MODULE = 1

• DEPENDENCY = 2

Used in: VMStatus

• repeated VMVerificationStatus status_list = 1

This is used to prove validator changes. When a validator is changing, it triggers an event on /validator_change_account/events/sent. To tell the client about validator changes, we query /validator_change_account/events/sent to get all versions that contain validator changes after the version that we are trying to update from. For each of these versions, the old validator set would have signed the ledger info at that version. The client needs this as well as the event results + proof. The client can then verify that these events were under the current tree and that the changes were signed by the old validators (and that the events correctly show which validators are the new validators). This message represents a single validator change event and the proof that corresponds to it

Used in: UpdateToLatestLedgerResponse

• optional LedgerInfoWithSignatures ledger_info_with_sigs = 1

• optional EventWithProof event_with_proof = 2

Protobuf definition for the Rust struct ValidatorPublicKeys

Used in: ValidatorSet

• bytes account_address = 1

  Validator account address

• bytes consensus_public_key = 2

  Consensus public key

• bytes network_signing_public_key = 3

  Network signing publick key

• bytes network_identity_public_key = 4

  / Network identity publick key

Protobuf definition for the Rust struct ValidatorSet.

• repeated ValidatorPublicKeys validator_public_keys = 1

Used in: LedgerInfoWithSignatures

• bytes validator_id = 1

  The account address of the validator, which can be used for retrieving its public key during the given epoch.

• bytes signature = 2

Write Operation on underlying storage.

Used in: WriteSet

• optional AccessPath access_path = 1

  AccessPath of the write set.

• bytes value = 2

  The value of the write op. Empty if `type` is Delete.

• WriteOpType type = 3

  WriteOp type.

Type of write operation

Used in: WriteOp

• Write = 0

  The WriteOp is to create/update the field from storage.

• Delete = 1

  The WriteOp is to delete the field from storage.

Set of WriteOps to save to storage.

Used in: RawTransaction

• repeated WriteOp write_set = 1

  Set of WriteOp for storage update.