On-Chain Analysis · 26 February 2026 · 9 min read

Signed Messages as Wallet Control Evidence

A signed message proves control of a key at a moment in time. It does not prove ownership, and the file is built to keep that distinction visible.

Signed messages are the most direct on-chain evidence of control. They are also frequently overasked: treated as proof of identity, proof of ownership, or proof of authority, none of which a signature actually carries on its own. DC-Services records signatures for what they support — control of a key at the moment of signing — and structures the file so that the question of ownership lives somewhere else.

What A Signed Message Proves

A signature over a message produced by a wallet's private key proves that the signer held the key at the time of signing. The verifier reproduces the verification with the address, the message and the signature, and either gets a match or does not. The arithmetic is unforgiving and that is the point.

The file records the message text, the address, the signature, the timestamp, the verification method and the verifier. A signature without a recorded verifier is a signature waiting to be verified, which is not the same as a verified signature.

Why The Nonce Matters

A signature over a generic message can in principle be replayed — supplied by someone other than the original signer at a later date. A signature over a message containing a counterparty nonce and a recent timestamp cannot be, because the nonce ties the signature to a specific verification request from a specific party at a specific time.

The counterparty supplies a unique nonce. The signer includes it verbatim in the signed message. The verifier checks the nonce, the timestamp and the signature together. Each piece is small; together they remove the easy attacks and leave the signature carrying the weight it is supposed to carry.

Control Is Not Ownership

Control of a key proves capability — the ability to authorise transactions from the address. Ownership is a separate, off-chain question about entitlement, contribution, beneficial interest and arrangements between parties. A signature settles the first and is silent on the second.

The file presents control evidence and ownership evidence in separate sections. Counterparties who need ownership confirmation are told what additional materials would actually support it, rather than being invited to read more into the signature than it supports.

Stale Signatures And Continuing Control

A signature from January supports control of the key in January. It does not, on its own, support control today. Keys are stolen, devices fail, controllers change. Continuing control requires fresh signing, ideally against a fresh counterparty nonce, on the date the question is being asked.

The file records the date of each signature and treats older ones as historical. Where current control matters — for a dispute, a transfer, a counterparty review — the request is for a fresh signature, and the file says so plainly rather than assuming yesterday's signature still applies.

When Signing Is Impossible

Sometimes the key cannot be signed with: a lost device, a deceased holder, hardware that no longer powers on. The file then moves to secondary evidence — device records, recovery artefacts, contemporaneous correspondence, on-chain spends from the address that demonstrate control was exercised in the relevant period.

None of the secondary materials equals a signed message, and the file does not pretend otherwise. They support a weaker claim, recorded as such, with the unresolved question — current control — left visible rather than assumed away.

Signed-Message Verification Checklist

Use a counterparty-supplied nonce, never a generic message.
Include a recent timestamp inside the signed message.
Record the address, message, signature and verification method.
Identify the verifier and the date of verification.
Treat signatures as point-in-time evidence of control.
Distinguish control from ownership explicitly in the file.
Request fresh signing where current control matters.

Frequently asked questions

What does a signed message actually prove?

That the signer held the wallet's private key at the moment of signing. The verifier reproduces the check with the address, message and signature. It is precise and limited to that moment in time.

Why include a counterparty nonce in the message?

It prevents replay. A nonce supplied by the verifier ties the signature to a specific verification request, so the signature cannot be reused as if it had been produced for somebody else later.

Does a valid signature prove ownership of the wallet?

No. It proves control of the key. Ownership is an off-chain question handled with off-chain evidence, and the file keeps the two in separate sections so the distinction is visible.

How long does a signed message stay useful?

It supports control at the moment of signing. Continuing control requires fresh signing. The file records dates honestly and treats older signatures as historical evidence rather than current proof.

What if the key cannot be signed with?

Secondary evidence is documented: device records, recovery artefacts, contemporaneous correspondence, on-chain spends from the address. The weaker claim is recorded as a weaker claim, and the unresolved question is left visible.

A signed message is small, precise and load-bearing — for exactly the question it answers. The file keeps the answer narrow and lets ownership be argued from its own evidence.