Overview

Typed message signing allows you to sign a message using standard formats prefixed with a specific string. Typed messages alone don't constitute a transaction but are often involved during the transaction signing process. They’re typically sent by Web3 dApps, and the approval notification in the Fireblocks mobile app displays a readable message. This signing method is safer than (and preferred over) Raw Signing because it helps mitigate the risk of users signing a valid but malicious transaction.

We support the following Typed Message formats:

• Bitcoin personal message: Used for Proof-of-Address ownership. This format can be used with the TRUST platform to assist with Travel Rule compliance.
• Ethereum personal message (ETH_MESSAGE): Primarily used for off-chain messages triggered by DeFi platforms, meta transactions, and Proof-of-Address ownership. This format can be used with the TRUST platform to assist with Travel Rule compliance.
• EIP-712 typed structured data (EIP-712): Similar to Ethereum personal message but uses a slightly more structured message format that provides more security.

Enabling Typed Message Signing

To use a dApp that requires you to sign in a Typed Message format, create a Typed Message TAP rule for that smart contract.

Using Typed Message Signing

When connecting to certain dApps, you receive a typed message to your mobile device. You can sign this off-chain message to connect and use the dApp. Typed Message Signing does not trigger any blockchain transactions or gas fees. Typed messages also appear in the Recent activity panel and your Transaction History.

Initiating Typed Message Signing

You can also initiate Typed Message Signing via the Fireblocks API. Learn more on our Developer Portal.