BTC message signing can prove to a third party that you control a BTC address without sending an on-chain transaction. Because wallets, address types, and verification tools do not always support the same message signature formats, imToken provides the following three formats in the "Sign Message" feature for BTC accounts:
standard: A traditional message signature format that is compatible with most wallets and services. It is suitable for platforms that only support the legacyBitcoin Signed Messageverification flow.BIP-137: A format that extends the traditional approach by distinguishing more address formats. It is suitable for hardware wallets such as Trezor and Ledger, and for platforms that explicitly requireBIP-137.BIP-322: A more general message signing scheme. It is suitable for platforms that explicitly requireBIP-322, or scenarios that need broader address / script compatibility.
How Do I Choose a Signature Format?
Use the following order when choosing a format:
- If the verifier explicitly requires a format, choose that format.
- If the verifier does not specify a format, refer to the common scenarios below. If you are still unsure, confirm the supported format with the verifier first.
- If verification fails after signing, first check whether the message, address, and signature format match the verifier's requirements.
Common Verification Scenarios
| Verifier / Scenario | Format to Refer To | Notes |
|---|---|---|
The verifier explicitly requires standard, BIP-137, or BIP-322 | The required format | Follow the verifier's requirement. |
| Bitcoin Core's traditional message signing / verification flow | standard | Suitable for scenarios that verify signatures through the traditional Bitcoin Signed Message flow. |
| Verification flows related to hardware wallets such as Trezor and Ledger | BIP-137 | If the verifier requires another format, follow that requirement. |
| The verifier explicitly supports a more general BTC message signing scheme | BIP-322 | Suitable when BIP-322 is explicitly required or broader address / script compatibility is needed. |
| HashKey Exchange address verification | Follow the page requirements | HashKey Exchange provides BTC message signing guidance. If the page does not specify a format, confirm its supported format first. |