Some DeFi apps expect to receive the same signature for separate consecutive messages. Signature caching allows the most recent signature to be returned based on the content and the source, including the workspace ID, Vault account, and asset, or derivation path. This signature may be returned repeatedly, skipping additional approval and signing processes.
Signature caching is enabled for all users by default using WalletConnect or the Fireblocks Chrome Extension. However, you can opt out by contacting Fireblocks Support.
Signature caching also works with Typed Messages and Raw Signing via the Fireblocks API.