Skip to content

feat: Decouple Key provider Architecture #83

Description

@mitfik

The current Signer struct fundamentally requires PrivateKey in memory. This makes it impossible
to support:

• HSMs (keys never leave hardware — only sign() calls travel over the wire)
• Cloud KMS (AWS KMS, GCP KMS, Azure Key Vault — private key never exists locally)
• Android Keystore / Secure Enclave (keys bound to hardware TEE/StrongBox)

The abstraction must be signing capability, not seed storage. A standalone crate should define this
interface with zero dependency on keriox.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions