Bitcoin message signer for wallet verification
When HashKey or OSL asks you to verify a self-custody Bitcoin address, use your wallet to sign the exact message shown by the exchange. This tool checks that the signature matches the message and the address before you copy it.
Privacy and signing safety
The message, address and signature stay in your browser and wallet. This page never asks for your seed phrase or private key. A message signature cannot move funds. Read the exact text before approving because it is a statement made with your wallet.
How to sign the verification message
- Keep the exchange’s verification screen open. Paste its current message here, then check the Bitcoin address against the one shown by the exchange. If the message does not include an address, enter it separately.
- Connect your wallet, confirm the address matches and review the exact message. Choose BIP-322 and approve the message in your wallet.
- Copy the verified signature into the exchange’s verification field. On a phone, compare the first and last six characters after pasting.
Hong Kong exchange information
Frequently asked questions
Which signature format should I choose?
Start with BIP-322, especially for a Taproot address beginning with bc1p. For addresses beginning with 1, 3 or bc1q, OKX Wallet also offers legacy ECDSA. If an exchange specifically expects the Native SegWit header, you can try the Trezor-style variant when it is available.
Why did the exchange reject a verified signature?
Local verification confirms the signature matches the address and text. The exchange may require a different format or a new challenge. Reopening the HashKey verification screen can generate a new serial code. Keep the screen open and sign the latest text exactly as shown.