Module holochain_zome_types::signature[][src]

Expand description

Signature for authenticity of data

Structs

The output of ephemeral signing. The private key for this public key has been discarded by this point. The signatures match the public key provided but cannot be reproduced or forged because the private key no longer exists. The signatures match the input items positionally in the vector, it is up to the caller to reconstruct/align/zip them back together.

Input structure for creating a signature.

Ephemerally sign a vector of bytes (i.e. a Vec<Vec>) Each of the items of the outer vector represents something to sign and will have a corresponding Signature in the output. The public key for the ephemeral operation will be returned in the output. Structurally mirrors/complements the Signature struct as a new type. There we know the key on the input side, here we receive the key on the output.

The raw bytes of a signature. The equality is not different, it’s just constant time, so we can derive a hash. For an actually secure thing we wouldn’t want to just assume a safe default hashing But that is not what clippy is complaining about here.

Mirror struct for Sign that includes a signature to verify against a key and data.

Constants

Ed25519 signatures are always the same length, 64 bytes.