The claim class: a project, exchange, or individual states that a specific wallet address belongs to them, usually to support a related claim, such as disclosed reserves, a treasury balance, or an official communication channel.
Claim class: a pattern of statements, not one attributed, dated quote.
Receipt to pull The receipt is a signed message: a specific piece of text, signed by the private key controlling the claimed address, that any reader can independently verify resolves to that address using a standard signature-verification tool, without the signer ever revealing the private key itself. No single receipt is linked: this piece explains how to check this kind of claim and does not grade one specific claim.
A valid signed message proves whoever produced it controls the private key (or, for a smart-contract wallet, meets its approval conditions) at the time of signing. It does not prove the signer is who they claim to be in the real world, only that they control the address in question, and it says nothing about the address's balance, history, or any other claim being made about it beyond ownership itself.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker.
Anyone can claim a wallet address belongs to them. Proving it, without handing over the private key, is exactly what a cryptographic signature is for, and checking that signature is a lot simpler than it sounds.
The Claim
The claim class: a project, exchange, or individual states that a specific wallet address belongs to them, usually to support a related claim, such as disclosed reserves, a treasury balance, or an official communication channel.
The Receipt
The receipt is a signed message: a specific piece of text, signed by the private key controlling the claimed address, that any reader can independently verify resolves to that address using a standard signature-verification tool, without the signer ever revealing the private key itself.
For wallets that are themselves smart contracts rather than simple externally owned accounts, such as many multi-signature or custodial wallets, standard message signing works differently and is typically verified through a smart-contract-based signature standard instead of the simpler scheme used for ordinary wallets. Checking which kind of address is involved matters before picking the right verification method.
What It Doesn’t Prove
A valid signed message proves whoever produced it controls the private key (or, for a smart-contract wallet, meets its approval conditions) at the time of signing. It does not prove the signer is who they claim to be in the real world, only that they control the address in question, and it says nothing about the address’s balance, history, or any other claim being made about it beyond ownership itself.
How to Check It Yourself
- Find the specific signed message and the exact text it covers, published through the project’s own official channel.
- Use a standard, independent signature-verification tool to check that the message and signature together resolve to the claimed address.
- If the address is a smart-contract wallet rather than a simple account, confirm the appropriate contract-based signature standard was used rather than assuming a simple scheme applies.
- Check that the signed message’s content actually states the specific claim being made (for example, naming the exact address and its claimed purpose) rather than generic, reusable text.
- Cross-check the channel that published the signature against the project’s established, long-standing communication channels.
- Treat an unsigned claim of ownership, with no verifiable signature at all, as unconfirmed rather than assuming good faith.
A Worked Example
A project states a specific address is its official treasury wallet. Alongside that claim it publishes a signed message, naming the address and its stated purpose in the signed text itself, and a reader runs that message and signature through a standard verification tool, confirming it resolves to the claimed address. That confirms control of the address by whoever signed; it says nothing about whether that person works for the project in any formal sense beyond what the project’s own channel already implies.
What Supported, Contradicted, and No Receipt Look Like
Supported: A signed message, published through the project’s established channel, independently verifies against the claimed address using a standard verification tool, and its text specifically states the claim being made.
Contradicted: The signature does not verify against the claimed address, or the signed text does not actually cover the specific claim being attributed to it.
No receipt: The project asserts ownership of an address with no signed message or equivalent on-chain attestation at all, leaving the ownership claim unconfirmed.
Red Flags
- An address is claimed as official with no signed message, only a statement on a social account.
- A signed message exists but uses generic text that does not specifically name the claim it is supposedly supporting.
- The claimed address is a smart-contract wallet, but a simple externally-owned-account signature method was used rather than the contract-appropriate standard.
- The channel publishing the signature has no established history connected to the project.
- A verification tool shows the signature does not resolve to the claimed address at all.
A Practical Complication to Expect
Standard message-signing schemes bind a signature to the exact text signed, which means a message proving ownership for one specific purpose, naming one specific address and one specific claim, cannot be reused to prove a different, unrelated claim about a different address, even by the same party. Readers should check that the signed text itself actually names the specific address and specific assertion currently being evaluated, rather than accepting an old, differently worded signed message as if it still applied to a newer claim the project is making today. Projects that change wallets over time should, ideally, sign a fresh message for each new address rather than relying on a single historical signature to vouch for an address it never actually named.
Why It Matters
Ownership of an address is the foundation underneath many other claims in this series, from disclosed reserves to treasury balances, and a signed message is one of the few places in crypto where cryptography itself, rather than reputation, can settle the question directly. It is also worth remembering that a signed message is a one-way, non-repudiable statement: once published, anyone can verify it indefinitely, which is part of why it remains a useful receipt long after the original announcement has scrolled out of view on whatever channel first carried it.
See our piece on exchange disclosed wallet holdings for how this mechanism supports a related claim.
FAQ
Do I need any special software to verify a signed message?
Standard, widely available signature-verification tools can check a message and signature against a claimed address without any special setup; the project publishing the signature should point to one or make the check straightforward.
Why would a smart-contract wallet need a different verification method?
A smart-contract wallet does not hold a single private key the way a simple account does; its approval logic is defined in code, so verifying a signature for it requires a standard built specifically to check approval through that contract’s own logic.
Does a signed message expire?
Not inherently, unless the message’s own text specifies a validity period; a signature proves control at the time of signing, which is why the signed text itself, including any date or context it states, matters as much as the signature’s validity.
Can someone sign a message proving ownership of an address they stole?
Yes; a signature proves key control, not legitimate acquisition. It answers “does this address belong to whoever is making this specific claim,” not broader questions about how that control was obtained.
What if a project uses a different signing method than the standard one most verification tools expect?
Some wallets and services support more than one signing standard, and a project using a less common method may need to point readers to a specific, compatible verification tool rather than assuming every general-purpose tool will handle it correctly. If a signature fails to verify using a standard tool, it is worth checking whether a different, compatible method was used before concluding the signature itself is invalid, since a tooling mismatch and an actually invalid signature produce the same unhelpful result to an unfamiliar reader.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker; we describe how a claim like this can be checked, never whether to buy, sell, or hold anything on the back of it.
Sources
This piece links no outside source: it explains a class of claim and the public records you would check, rather than grading one specific statement. When a specific claim is checked, every source link is listed here with its status.
Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.



