SigningDriver

interface SigningDriver

Produces Canton CryptoOuterClass.Signatures over ledger-provided hashes.

Implementations decide where the private key lives: in software, in the Android Keystore / StrongBox (see the android module), or in a custody provider (Fireblocks, BitGo, ...). The driver never sees a full transaction — only the hash the ledger asks the party to sign, which is what makes hardware-backed and custody-held keys possible.

The returned signature carries no signed_by fingerprint; callers that know the canonical fingerprint (e.g. from GenerateExternalPartyTopologyResponse.public_key_fingerprint) complete it via CryptoOuterClass.Signature.toBuilder.

Inheritors

Functions

Link copied to clipboard
abstract suspend fun publicKey(): CryptoOuterClass.SigningPublicKey

The public key in a Ledger-API-compatible encoding.

Link copied to clipboard
abstract suspend fun sign(bytes: ByteArray): CryptoOuterClass.Signature

Signs bytes (a Canton-provided hash) with the driver's private key.