@polymeshassociation/signing-manager-types v3.4.2

Polymesh Signing Manager Types

This defines the types needed to implement a Polymesh SDK signing manager, along with exporting some commonly needed utilities for implementations

A signing manager abstracts the cryptographic signing of transactions so the SDK is indifferent to where and how private keys are stored.

Implementations

• Browser Private keys are saved in a browser extension
• WalletConnect Formerly WalletConnect adaptor (rebranded to Reown)
• Local Private keys are loaded into memory for backend environments like Node.js
• Hashicorp Vault Private keys are stored in a Vault transit engine

The signing manager API allows for more specialized signers to be implemented. The linked packages are not reccomended for general use and require access to a 3rd party API. Linked for completness, and to provide examples for more advance use cases.

Custom Implementations

• Azure Keys are held in Microsoft Azure
• Fireblocks Keys are held in Fireblocks
• Approval Demonstrates a "cold wallet" type approach