tendermint/crypto

Table of Contents

tendermint/crypto/keys.proto

Top

PublicKey

PublicKey defines the keys available for use with Tendermint Validators

FieldTypeLabelDescription
ed25519 bytes

secp256k1 bytes

tendermint/crypto/proof.proto

Top

DominoOp

FieldTypeLabelDescription
key string

input string

output string

Proof

FieldTypeLabelDescription
total int64

index int64

leaf_hash bytes

aunts bytes repeated

ProofOp

ProofOp defines an operation used for calculating Merkle root

The data could be arbitrary format, providing nessecary data

for example neighbouring node hash

FieldTypeLabelDescription
type string

key bytes

data bytes

ProofOps

ProofOps is Merkle proof defined by the list of ProofOps

FieldTypeLabelDescription
ops ProofOp repeated

ValueOp

FieldTypeLabelDescription
key bytes

Encoded in ProofOp.Key.

proof Proof

To encode in ProofOp.Data

Scalar Value Types

.proto Type Notes Python Type
double float
float float
int32 Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint32 instead. int
int64 Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint64 instead. int/long
uint32 Uses variable-length encoding. int/long
uint64 Uses variable-length encoding. int/long
sint32 Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int32s. int
sint64 Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int64s. int/long
fixed32 Always four bytes. More efficient than uint32 if values are often greater than 2^28. int
fixed64 Always eight bytes. More efficient than uint64 if values are often greater than 2^56. int/long
sfixed32 Always four bytes. int
sfixed64 Always eight bytes. int/long
bool boolean
string A string must always contain UTF-8 encoded or 7-bit ASCII text. str/unicode
bytes May contain any arbitrary sequence of bytes. str