What is the Verify Bitcoin Signed Message?
A signed message is how someone proves they own a Bitcoin address without moving any coins. Exchanges, buyers and auditors ask for it. The owner signs a short text with their wallet, and anyone can check the signature against the address.
Paste the message, the address and the signature, and this tool tells you whether they match. It supports the standard format used by Bitcoin Core, Electrum, Sparrow and most hardware wallets, for legacy (1...), nested SegWit (3...) and native SegWit (bc1q...) addresses.
The check runs in your browser. Taproot (bc1p) signatures use a newer method, BIP322, which this tool does not check yet.
Features
Standard signatures
The usual 65-byte base64 signature from Bitcoin Core, Electrum, Sparrow and hardware wallets.
Three address types
Legacy, nested SegWit and native SegWit, including Electrum style SegWit signatures.
No keys needed
Verifying needs only public data. Nothing is sent.
Clear answers
Valid or invalid, with the most common reason when it fails.
How to use the Verify Bitcoin Signed Message
- 1
Paste the message exactly as it was signed, with the same spaces and line breaks.
- 2
Paste the Bitcoin address and the signature.
- 3
Press Verify.
Who it is for
Proof of ownership
A seller proves the address holding the coins is theirs.
Exchange checks
Confirm a withdrawal address belongs to the customer.
Audits
Check signed statements from a fund or company.
Tips for better results
- Copy the message exactly. One extra space or a different line break makes it fail.
- Ask for a message with today's date in it, so an old signature cannot be reused.
Questions people ask
How do I sign a message?
In Electrum: Tools, Sign/verify message. In Sparrow: Tools, Sign/Verify Message. In Bitcoin Core: File, Sign message. Then send the text, the address and the signature.
Why is there no Sign button?
Signing needs your private key. Typing a key into any web page is risky, so sign in your own wallet (Electrum, Sparrow, Bitcoin Core) and use this page only to check.
It says invalid, but I am sure it is right.
The message must match character for character. A missing full stop, an extra space or a different line break makes it fail.