Digital Asset Records · 18 March 2026 · 9 min read

Self-Custody Wallets and the Evidence-of-Control Problem

Holding the keys is not the same as proving you hold them, especially years later. DC-Services structures control evidence around what actually survives scrutiny.

Self-custody removes the venue from the picture and replaces it with a problem: the holder must demonstrate control of the keys when somebody else asks, sometimes years after the wallet went quiet. The available evidence — signed messages, device records, recovery artefacts, exchange withdrawal links — each carries different weight, and using the wrong one produces a file that looks confident and fails on the first push.

What 'Control' Means In Practice

Control of a wallet means the ability to produce a transaction or signature using the private key. The chain is willing to demonstrate this on request: a signed message proves the signer held the key at the moment of signing. What the chain will not demonstrate is who that signer is, or that control existed before or after the signing moment.

The file records control as a point-in-time fact tied to a specific signature or transaction, rather than as a general claim about the wallet. A signature from January does not, on its own, prove control in March, and the document refuses to imply that it does.

Signed Messages As The Primary Tool

A signed challenge — typically a short message including a unique nonce and a timestamp, signed by the wallet's private key — is the most direct evidence of control. It is verifiable by anyone with the address and the message, and it cannot be produced without the key.

The file records the message text, the address, the signature, the timestamp and the verification method. Where the message includes a counterparty's nonce, that nonce is preserved so the recipient can confirm the signature was produced for them rather than reused from elsewhere.

Device And Recovery Evidence

Where signing is impractical — a lost device, a deceased holder, a hardware wallet that no longer powers on — secondary evidence becomes relevant: device serial numbers, recovery seed metadata, purchase records, contemporaneous correspondence about the wallet's existence and use.

Each piece is recorded for what it is. A device serial supports the existence of the wallet hardware; a purchase record supports acquisition; correspondence supports awareness and use. None of them, individually or together, equals a signed message. The file shows the hierarchy rather than averaging it.

Linking Wallets To Off-Chain Identity

Control evidence is most useful when the wallet can also be tied to a specific person or entity. Exchange withdrawals into the wallet's first-received address, KYC-bound deposits, recurring patterns that match known activity, and signed messages produced under contemporaneous verification all contribute.

The file builds the linkage from documented events rather than inference. Each link is recorded with its source and its date. Where the linkage chain is partial, the missing piece is named, so the reader is not asked to assume the bridge exists.

What The File Cannot Establish

Even a strong control file does not establish legal ownership. Control of a key proves capability, not entitlement. Legal ownership depends on the source of the asset, the relationship between the holder and any contributors, and arrangements that may exist off-chain — none of which the wallet itself reveals.

The deliverable records the control evidence available, the identity linkage available, and the ownership question as a separate matter requiring its own evidence. Counterparties who need ownership confirmation are told what additional materials would actually support it.

Self-Custody Control Evidence Hierarchy

Evidence type	What it supports	What it does not
Signed message with nonce	Control of address at signing time	Continuing control or ownership
Recent on-chain spend	Control at spend time	Identity of the controller
Device serial / purchase record	Existence and acquisition of hardware	Possession of the key today
Recovery seed metadata	Existence of a backup pathway	That the backup remains accessible
Correspondence about the wallet	Awareness and use over time	Continuing control

Frequently asked questions

What is the strongest form of control evidence?

A signed message containing a counterparty nonce and a recent timestamp, verifiable by the recipient. It proves the signer held the key at the moment of signing, which is what control evidence is actually about.

What if the holder cannot sign a message?

Secondary evidence — device records, recovery artefacts, contemporaneous correspondence, on-chain spends from the address — is documented in its own hierarchy. None of it equals a signed message, and the file shows the difference rather than averaging it.

Does proving control prove ownership?

No. Control proves capability. Ownership depends on the source of the asset and the arrangements between the parties involved, which are off-chain questions handled with off-chain evidence.

How long does a signed message remain useful as control evidence?

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

How is a wallet tied to a specific person?

Through documented links — exchange withdrawals from KYC-verified accounts, signed messages produced under verification, contemporaneous correspondence. The chain is built from records, not assertion, and the file states where the chain is partial.

Self-custody puts the holder in charge of the keys and the evidence at the same time. The file works when control is treated as a point-in-time fact and ownership is treated as a separate question — and falls apart whenever those two get blurred.