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 turned on for all users by default using WalletConnect or the Fireblocks Chrome Extension for DeFi integration, though you can opt out by contacting Support.
Workspaces with the cached signatures feature enabled will experience the same while signing Typed and RAW messages via the API