NovA provider may ask for evidence that you control the wallet
Why an address history may not prove who controls a wallet, and where proof of control can enter a property settlement route.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
A clean transaction history and control of a wallet answer different questions. A blockchain record can show what happened to an address, but the address itself does not name the person who can authorize a transfer today. That is why a provider may sometimes ask a property buyer to establish not only where the digital assets came from, but also that the buyer actually controls the self-hosted wallet involved in the route.
This distinction matters when a digital asset is expected to become a completed property payment. The route may pass through an exchange, an over-the-counter provider, a bank and finally the contractual recipient. A wallet can be technically accessible while one of those parties still requires an additional ownership or control check before funds move.
Two different proofs enter the route at different points
An address history can help explain the source and movement of funds. It may show that an asset was acquired years ago, transferred between addresses, received from another person or converted from another asset. That can be relevant to a source-of-funds explanation.
Control is a separate question. Imagine a buyer presents an address holding enough assets for the next property payment. The chain shows that the balance has remained there for a long time. None of that, on its own, proves to a regulated provider that the buyer has the credentials needed to move the funds.
The reverse is equally important. A buyer might be able to prove current control of a wallet while the origin of the balance remains unexplained. A control check does not establish the full source-of-funds story. Treating one as a substitute for the other creates a gap precisely where the payment route is supposed to become more transparent.
A property transaction has its own identities and obligations: the buyer, the contractual recipient, the amount due, the currency of the obligation and the date by which payment has to be credited. The crypto leg of the route is only one part of that structure.
Consider a hypothetical route in which a buyer sends digital assets to a regulated provider, the provider converts them into fiat currency and a bank then sends the resulting amount to the developer. Evidence of wallet control concerns the first part of the chain. Evidence that the developer has credited the payment concerns the last part.
The mistake is to ask one record to prove everything. An on-chain transaction hash does not automatically show that a seller received the contractual amount in the required currency. A bank receipt at the end does not, by itself, explain the earlier origin of the digital assets.
Andrey Arbenin's current NovAsia profile makes the same practical distinction: the viability of a route depends on the bank, payment service, exchange, jurisdiction, source of funds and the recipient's contractual terms. The useful task is therefore not to invent one universal “crypto payment file”, but to understand which party requires which evidence.
Proof of control can take different forms
The procedure is provider- and jurisdiction-specific. One clear regulatory example comes from the European Union. Regulation (EU) 2023/1113 requires relevant crypto-asset service providers to take measures, in specified transfers above EUR 1,000 involving a self-hosted address, to assess whether that address is owned or controlled by their client.
That EU rule should not be presented as a worldwide threshold. It is useful here because it demonstrates why a provider may legitimately distinguish a known transaction history from proof of address control.
Operational methods vary as well. Coinbase, for example, describes wallet-message signatures and, in some cases, a small verification transfer as methods used in its self-hosted wallet verification flows. Those are examples from one provider, not instructions that apply to every exchange or wallet.
One boundary should remain clear throughout the process: proving control is not the same as handing control to someone else. A buyer should never treat a request for a seed phrase, private key, password or authentication code as a normal way to document a property payment. A legitimate provider may have a defined verification process, but the evidence process should not require surrendering the secret that can move the assets.
The verification step belongs before the deadline
Digital-asset routes can look extremely fast if the only clock being measured is the blockchain transaction. A property buyer has to account for the time before that transaction: onboarding, identity checks, source-of-funds review, wallet verification, recipient checks and any conversion or banking steps.
That is why a control requirement discovered after a deposit has been committed can become a transaction problem even though nothing is wrong with the wallet itself. The buyer may simply have selected a route whose documentary conditions were not understood early enough.
Before relying on a route for a contractual date, I want to know whether a self-hosted wallet needs separate verification, whether the provider needs information about the recipient, and what event the provider treats as completion of its checks. None of those questions predicts that the transfer will clear. They tell the buyer how much of the route is known before the deadline starts to matter.
A useful payment file is a chain, not one perfect document
The final record may contain several different pieces: evidence supporting the source of the assets, evidence of wallet control where it was required, transaction records, a conversion record, the fiat transfer and the recipient's acknowledgement that the payment was credited.
Some routes will not need every item. Others will require additional documents. The right set comes from the actual contract and the institutions involved, not from a generic crypto checklist.
The practical discipline is to label each piece of evidence by the question it answers. Wallet history explains movement. A provider's control-verification step links the customer to a self-hosted address. A conversion record fixes the point at which the digital asset became the settlement currency. A bank record shows the fiat leg. The seller's written confirmation closes the property-payment question.
Once those functions are separated, a request to prove wallet control becomes less mysterious. It is not an accusation and it is not proof that a route will succeed. It is one possible documentary step in a longer settlement chain.
Sources
- NovAsia — “Andrey Arbenin — international transfers and digital assets”, profile updated 10 July 2026; accessed 6 October 2026.
- Financial Action Task Force — “Virtual Assets”, on customer due diligence, record keeping and originator/beneficiary information; accessed 6 October 2026.
- EUR-Lex — Regulation (EU) 2023/1113, Articles 14 and 16 on crypto-asset transfers involving self-hosted addresses; accessed 6 October 2026.
- Coinbase Help — “Self Hosted Wallet Verification” and “Coinbase Europe Travel Rule Regulations”, provider-specific examples of self-hosted wallet verification; accessed 6 October 2026.