Module indy::api::signus

Functions

indy_create_and_store_my_did	Creates keys (signing and encryption keys) for a new DID (owned by the caller of the library). Identity's DID must be either explicitly provided, or taken as the first 16 bit of verkey. Saves the Identity DID with keys in a secured Wallet, so that it can be used to sign and encrypt transactions.
indy_decrypt	Decrypts a message encrypted by a public key associated with my DID. The DID with a secret key must be already created and stored in a secured wallet (see wallet_create_and_store_my_identity)
indy_encrypt	Encrypts a message by a public key associated with a DID. If a secure wallet doesn't contain a public key associated with the given DID, then the public key is read from the Ledger. Otherwise either an existing public key from wallet is used (see wallet_store_their_identity), or it checks the Ledger (according to freshness settings set during initialization) whether public key is still the same and updates public key for the DID if needed.
indy_replace_keys	Generated new keys (signing and encryption keys) for an existing DID (owned by the caller of the library).
indy_sign	Signs a message by a signing key associated with my DID. The DID with a signing key must be already created and stored in a secured wallet (see create_and_store_my_identity)
indy_store_their_did	Saves their DID for a pairwise connection in a secured Wallet, so that it can be used to verify transaction.
indy_verify_signature	Verify a signature created by a key associated with a DID. If a secure wallet doesn't contain a verkey associated with the given DID, then verkey is read from the Ledger. Otherwise either an existing verkey from wallet is used (see wallet_store_their_identity), or it checks the Ledger (according to freshness settings set during initialization) whether verkey is still the same and updates verkey for the DID if needed.