Cyber & Technology Law
Crypto lost during a Dubai OTC deal: who was responsible?
By Advocate Sharan Jain September 8, 2026

When crypto disappears during an over-the-counter transaction, the immediate legal question is not simply who held the wallet device. It is who undertook which obligation, who could actually control the assets and what caused the loss. A DIFC crypto custody loss claim can turn on the difference between a promise to exercise reasonable care and an obligation to deliver a result regardless of fault.
Preserve the transaction record before arguing about labels such as custodian, escrow agent or broker. Save the agreed process, every change to it, the wallet and payment identifiers and the communications immediately before the transfer. Do not disclose private keys or recovery secrets in a public complaint or an ordinary evidence bundle.
| Issue | Record to preserve | What it does not prove alone |
|---|---|---|
| Contracting party | Agreement, invoice and onboarding record | A brand name does not identify every liable entity |
| Transfer | Transaction hash, network and destination | An address does not by itself identify its legal controller |
| Wallet access | Device setup and authority chronology | Physical possession does not settle all access questions |
| Payment condition | Release instructions and banking records | A payment assurance is not proof of receipt |
| Loss | Asset movements, recovery and valuation records | A quoted market price is not automatically the damages measure |
What does the Gate Mena litigation actually establish?
It concerns a particular OTC transaction and an intermediary's role, not a universal rule for retail exchange accounts. Its later history is essential. Reading the successful part of an appeal without the retrial result would give a misleading picture.
The June 2024 appeal in Gate Mena v Tabarak, paragraphs 177-184 and the order, required a retrial of an unaddressed contractual issue. It did not award the missing crypto's value. The appeal against the individual defendant was dismissed.
At the 17 June 2026 retrial, [2024] DIFC DEC 002, paragraphs 192-202, the Court found a contract but rejected a strict obligation to return assets lost without fault. The applicable reasonable-care finding meant the claim was dismissed. That conclusion depended on the parties' agreed roles and the findings binding at retrial.
For a client, the useful preparation question is therefore specific: what in this transaction made the defendant responsible for this particular risk? The answer may lie in express terms, the service undertaken and the conduct before transfer. It cannot be supplied just by describing the missing asset as cryptocurrency.
Who exactly accepted responsibility for the transaction?
Identify the legal person in each role. Your seller, buyer, introducing broker, intermediary, exchange operator and wallet provider may be different entities. Start with the executed agreement, onboarding communications and invoices. Add any document showing that one company acted for another.
Do not assume an employee's presence makes that individual a party to the contract. Conversely, do not silently replace the contracting company with a better-known group company when drafting a demand. Record names and capacities as the contemporaneous documents describe them, then have any disputed agency or personal-liability argument assessed.
Construct a role sheet with one row per participant. State what each was supposed to receive, hold, verify, release or advise on. Identify the document supporting that description. Where nobody expressly accepted a task, mark the gap rather than allocating responsibility according to who appears most able to pay.
A licence or regulated status also needs careful use. Check the precise entity and authorised activity, but do not convert that status into a promise that it insured every transaction. The court's contractual analysis remains distinct from questions about regulatory permissions. This article does not determine whether any current business may lawfully provide a proposed crypto service.
What process was agreed before the assets moved?
Write the intended sequence as numbered events. For example, the parties may have contemplated receipt of coins, confirmation of cleared funds and then release to the buyer. Establish who was to confirm each event and what was meant to happen if payment failed. A diagram is useful only if every arrow corresponds to an actual instruction.
Compare that sequence with what happened on the day. Identify changed wallets, different recipients, revised commissions, additional people and altered payment assurances. An apparently minor logistical change can create a different control arrangement. Do not assume that an earlier approval covered everything that happened afterwards.
Preserve both the original plan and the change. Forwarded extracts can hide who proposed it and whether someone objected. Export the relevant conversation with its timestamps and participants where possible, while keeping the original device and account records intact. Note the time zone used by each source.
If instructions were oral, ask each witness to record their own recollection promptly without coordinating a collective version. Distinguish what they heard from what someone later told them. A witness who attended only the end of the meeting should not be presented as having observed the entire setup.
Original sequence
Identify the agreed custody, payment and release events. Tie each step to an instruction rather than an assumption about normal trading practice.
Changed sequence
Mark new wallets, participants and payment conditions. Preserve who proposed each change, who accepted it and what objections were made.
Actual sequence
Align communications, banking events and blockchain movements by time. Keep observations separate from explanations supplied after the assets disappeared.
Does holding the device mean controlling the crypto?
Do not use physical possession as a substitute for a technical account of access. Establish how the wallet was created, who supplied the device and which people participated in its setup. Identify any recovery or duplicate-access issue for an appropriately qualified technical reviewer.
The important distinction is between a fact and an inference. A photograph may show a device in a safe. It does not, without further technical evidence, answer every question about the ability to move the associated assets. Equally, an unexplained transfer does not by itself prove that the person holding the device authorised it.
Preserve model and software details that can be collected safely without changing the evidence. Record who examined or handled the device after the incident and what they did. Avoid repeated informal demonstrations on the original equipment merely to see whether a theory works.
Protect secrets while preserving evidence. Tell the legal and technical reviewers that relevant access material exists and agree a secure handling method. Public transaction identifiers can often be discussed without circulating recovery phrases. Do not paste confidential access credentials into a general complaint, social post or shared working document.
Common mistake. Writing that a person controlled the crypto solely because they held the hardware. Describe the observed custody separately from the technical and legal conclusions that still need evidence.
Was the promise to take care or to guarantee the result?
Read the precise undertaking before treating the disappearance as proof of breach. A duty to use reasonable care asks about the quality of the performance required. A strict obligation may allocate the loss even where reasonable care was taken. The distinction must come from the applicable contract and law, not an assumption that every intermediary supplies insurance.
Look for terms dealing with release, return, unauthorised transfers, fraud, client instructions, third-party systems and exclusions. Read them together with definitions and the service description. If the wording is unclear, identify the competing interpretations and the transaction facts each requires.
Do not stop at a sentence saying that assets must be returned if payment does not arrive. Ask what the agreement says about the disputed circumstance: assets no longer available because of an alleged fraud, operational failure or instruction. Whether the return promise answers that circumstance is a question for proper interpretation.
It is useful to prepare two separate evidential routes for review. One asks whether the defendant promised the result alleged. The other asks what specific careless act or omission occurred and how it caused the loss. If neither route can be described without general accusations, further investigation may be needed before a monetary demand is properly formulated.
What if the original onboarding condition was never completed?
Retain the onboarding terms, payment conditions and later conduct. A dispute may concern whether the original agreement took effect, whether the parties altered it or whether another agreement arose through what they did. Those are different explanations, even where they concern the same meeting.
The Gate Mena appeal shows why an alternative contractual case cannot simply be ignored. Its remitted questions included whether a contract arose, what its terms were and whether they were breached. A finding that some contract existed would still leave the contents and performance questions to be answered.
For your file, identify any fee agreed at the transaction stage and the service for which it was to be paid. Preserve the offer, acceptance, authority and subsequent performance. An unpaid fee, changed commission or unsigned onboarding form should be placed in the chronology rather than treated as conclusive in isolation.
Keep proposed legal characterisations out of the raw witness record. A witness can say that a participant agreed to a revised commission before the transfer. Whether that conduct created, varied or performed a contract is a separate legal analysis. Maintaining that distinction makes it easier to test alternatives without rewriting the facts to fit them.
How do I distinguish fraud from a breach by the intermediary?
Separate the alleged dishonest conduct from the claim against the person you contracted with. A third party's wrongdoing may explain the loss, but the intermediary's liability still depends on the duty and breach alleged against it. The existence of fraud does not automatically answer who bears the loss.
Write the causal sequence in plain language. Identify the instruction, access event or omitted check said to have enabled the movement. Then identify the evidence supporting that step. If an expert has not established how the assets moved, state the hypothesis as a hypothesis.
Avoid accusing every participant of collusion simply because the explanation is incomplete. Record suspicious facts precisely, including inconsistent statements or unexplained access, without asserting a criminal conclusion that the evidence does not establish. Preserve alternative explanations for testing.
Consider the counterfactual operationally. If the alleged missing check had been performed, what would have been discovered and what could then have been done? If the complaint is that a transfer occurred before payment, identify who authorised the sequence and the payment verification required. This is more useful than a general statement that a reputable intermediary should have prevented the loss.
What should a technical expert be asked to establish?
Give the expert a defined question and a reliable evidence set. Useful questions may concern the observed asset movements, the wallet functionality relevant at the time and whether a proposed access explanation is technically possible. Avoid asking for a broad report proving that the defendant was negligent before the factual mechanism is understood.
Under RDC Part 31, particularly Rules 31.3-31.9 and 31.13, court expert evidence involves an overriding duty to assist the Court, independence and requirements concerning scope and permission. A litigation report is not simply a party's technical argument with an expert's signature added.
Ask the reviewer to identify assumptions and missing material. A report based on screenshots alone should not quietly assume access to original logs. If an experiment uses a different software version or device, the difference needs explanation. Preserve reproducible observations without implying that a laboratory reconstruction necessarily proves what happened at the original meeting.
Separate asset tracing from identification. A sequence of addresses may demonstrate movement while leaving questions about the person behind them unresolved. Record the source and confidence of any attribution. A label supplied by an analytics tool should not become an unquestioned legal identity in the pleading.
Budget for the issue that matters. If contractual interpretation disposes of the asserted strict-return claim, an elaborate technical investigation may not answer that legal question. Conversely, a reasonable-care claim may depend on technical matters that cannot be resolved by reading the contract alone. Scope the two workstreams together.
Can the Digital Economy Court hear any Dubai crypto dispute?
Do not assume that the presence of a digital asset supplies every jurisdictional requirement. RDC Part 58, Rules 58.3-58.7, identifies the Digital Economy Court as a specialist division and describes suitable digital-economy claims, including digital assets and relevant platforms. Classification within that division is not the same task as establishing the DIFC Courts' jurisdiction over the defendant and dispute.
Have the underlying gateway assessed under the applicable jurisdiction law and any agreement. The official English version of Dubai Law No. 2 of 2025, Article 14, sets out jurisdictional routes. The document states that Arabic prevails. Location of a meeting, a brand's Dubai presence and an express court agreement should not be treated as interchangeable evidence.
Prepare the forum documents early: the signed dispute clause, relevant entity records and the contract's connection with the DIFC. If another court or arbitration is specified, provide the exact clause. Do not omit it because a specialist digital-assets court appears more convenient.
Urgent preservation or protective relief is a separate question requiring assessment of the proposed defendant, assets, evidence and applicable tests. This article does not promise that a freezing order or transfer reversal will be available. A court order and actual recovery from a person or platform are different stages.
How should I calculate the claim without overstating the loss?
Start with the asset quantity and movements, then address monetary valuation separately. Identify what left, what was received in exchange, what remains recoverable and what has already been returned. Distinguish an executed transfer from an intended trade that never completed.
Keep source records for prices and exchange rates at relevant dates. Do not choose the highest later price as the obvious answer. The legally relevant valuation date and measure require assessment of the claim, remedy and facts. State alternatives as alternatives, with transparent calculations.
For a hypothetical transfer of two units followed by recovery of half a unit, the unrecovered quantity is one and a half units. That arithmetic does not decide whether the claim is for return, monetary compensation or some other relief. Nor does it determine who bears a price change after the incident.
Keep investigation and recovery costs in their own schedule with invoices and reasons. Do not assume every expenditure is recoverable merely because it followed the loss. Record any settlement, reimbursement or insurance payment so that the same economic loss is not silently counted twice.
If you claim a lost trading opportunity, identify the evidence that the intended trade would have occurred and the resources available to perform it. A retrospective chart of a profitable market movement is not a contemporaneous trading instruction. Treat unsupported estimates as such when making commercial decisions about the dispute.
What belongs in the first evidence pack?
The first pack should let a reviewer reconstruct the transaction without asking you to narrate each screenshot. Use a short chronology linked to numbered records. Retain the originals and provide working copies with confidential material handled appropriately.
- Identify each entity and its agreed transaction role.
- Save the executed terms, onboarding record and fee arrangements.
- Record the original transfer sequence and each agreed change.
- Preserve transaction identifiers, banking events and relevant communications.
- Secure devices and access material without unnecessary experimentation.
- Separate observed facts, witness recollections and technical hypotheses.
- Prepare an asset and loss schedule including recoveries.
- Obtain prompt review of forum, deadlines and any urgent protective measures.
Add a questions page rather than hiding gaps. State which records are missing, who may hold them and whether preservation requests have been considered. If a platform has acknowledged the incident, preserve the exact acknowledgment without describing it as an admission of legal liability.
Keep a contact log for communications after the loss. Record what each participant said they could do, what information they requested and any response dates. Do not let repeated informal assurances substitute for assessment of litigation time limits or available recovery routes.
A preservation request should identify records rather than invite an improvised investigation that changes them. For example, specify the relevant account, transaction window, communications and device-handling records. Ask the recipient to confirm what is being retained. Whether a particular person can be compelled to provide it is a separate procedural question, not something established by sending the request.
Maintain a simple evidence register showing the item, source, date obtained and location of the original. If a screenshot was made after an account display changed, state that timing. If two exports contain different timestamps or balances, preserve both and investigate the difference. Do not replace the earlier version merely because the later one looks clearer.
Finally, provide a list of immediate decisions: an expiring response date, a proposed settlement, requested access to a device or an instruction from an exchange. This helps the reviewer separate urgent choices from the longer task of establishing liability, without promising that every urgent request has a legal remedy.
Key takeaway. The asset movement proves an event. The contract, technical record and causation evidence must establish why a particular defendant is legally responsible for it.
Prove the movement
Preserve the asset quantity, network, transaction identifiers and subsequent recoveries. Identify gaps in attribution instead of filling them with assumptions.
Prove the undertaking
Find the terms and conduct defining the intermediary's task. Distinguish a return obligation, a care obligation and an alleged guarantee.
Prove the connection
Explain how the identified breach produced the claimed loss. Test the technical mechanism and disclose alternative explanations that remain unresolved.
Which questions does the judgment leave open?
The article deliberately does not resolve the general legal status of every token, every custody model or every platform. The 2026 retrial left broader issues unnecessary to its result. Its dismissal should not be converted into either immunity for intermediaries or a rule that custody claims never succeed.
Sources were checked on 29 September 2026, including the 2024 appeal, 2026 retrial and current rules linked here. The later-history search was bounded and does not establish that no further appeal has been filed. Confirm procedural status before relying on the judgment in proceedings.
For an actual transaction, qualified review must address the applicable law at the relevant dates, the particular asset and service, licensing questions, jurisdiction and limitation. No private keys or original devices should be handed over casually merely because someone offers recovery assistance. Preserve evidence and obtain a secure, defined plan before taking steps that could change it.
Frequently Asked Questions
Does losing crypto establish a claim against the intermediary? Not by itself. Establish the undertaking, breach and connection to the loss.
Did Gate Mena win compensation in the 2024 appeal? No. A contractual issue was remitted. The claim was dismissed at the June 2026 retrial.
Is physical possession of the wallet conclusive? No. Technical access and the actual control arrangement need separate evidence.
Must every intermediary guarantee return despite fraud? No universal rule is stated. The particular contract and allocation of risk require interpretation.
Should I put my recovery phrase in the evidence bundle? Do not put access secrets into a public or ordinary shared bundle. Arrange secure handling with the relevant reviewers.
Can every Dubai crypto claim go to the Digital Economy Court? Do not assume so. The underlying DIFC jurisdictional basis must also be established.
Can I demand the highest price reached after the loss? Not automatically. Obtain a claim-specific valuation analysis and preserve reliable price evidence.
Does the 2026 judgment settle every digital-assets issue? No. It decided a particular contractual dispute and left broader unnecessary issues unresolved.
This article is for general informational purposes only and does not constitute legal advice. Consult a qualified advocate for advice on your specific situation.
Related Guides
References
Matters before the DIFC Courts are conducted by the firm, with counsel from its panel of DIFC-registered advocates engaged for the hearing. The firm acts as counsel in arbitrations seated in the DIFC and the wider UAE, and conducts the Indian proceedings that follow, including enforcement of UAE awards and judgments in India. This section is legal information, not legal advice.
All Dubai and DIFC guides