A token project launches with three co-founders and a vesting schedule that allocates 15 per cent of the supply to the team over four years. Eighteen months in, one founder exits acrimoniously, the remaining two discover tokens have moved off-schedule, and the treasury multi-sig is suddenly contested. The question is not whether the vesting agreement was breached – it almost certainly was – but whether the remaining founders can freeze the tokens, compel their return and prevent further dissipation before the dispute destroys the project's credibility with investors and regulators. Co-founder and token vesting disputes sit at the intersection of corporate governance, contract enforcement and on-chain asset recovery, and the legal tools available turn on how quickly the dispute is escalated, where the entity sits, where the founders are, and whether the tokens are still traceable.
Co-founder disputes in crypto ventures differ from equity founder disputes in two material ways: the asset in question often moves faster than a court order, and the technical means of control – private keys, multi-signature wallet configurations, admin privileges on a smart contract – sit outside traditional notions of corporate authority. A departing founder who holds one key in a 2-of-3 treasury multi-sig may not be a director under the company's articles, but he controls a blocking vote on every on-chain transaction. A vesting contract written in Solidity may release tokens automatically on a time curve with no mechanism for clawback if the founder's employment terminates early. The legal problem is identifying which remedies can operate at the speed and across the jurisdictions the dispute demands, and structuring them so that a court in one forum can reach tokens held on an exchange in another or frozen at the contract level by an issuer in a third.
How founder disputes arise in token projects
Disputes typically emerge in one of three scenarios. The first is the voluntary departure where the departing founder argues the vesting schedule continues to run post-exit, the remaining founders argue cessation triggers forfeiture, and the documentation is ambiguous or entirely absent. In our cross-border practice, we see this pattern most often in projects that moved quickly from whitepaper to token generation event (TGE) without formalizing founder agreements or updating vesting logic once the tokenomics model changed. The second scenario is the contested removal: a founder is voted out by the other co-founders or by a board acting under shareholder authority, and the removed founder refuses to surrender control of keys, claims constructive dismissal or argues the removal was procedurally invalid under the company's governing law. The third is fraud or self-dealing: one founder uses access to move tokens inconsistent with the vesting schedule, diverts treasury funds to personal wallets or front-runs a listing by transferring unvested allocation to a nominee account and selling immediately.
The technical architecture of the project shapes the dispute as much as the contract terms. A project with vesting implemented entirely on-chain through an audited smart contract that the founders cannot override presents a narrow fact set: either the contract releases tokens according to its code or it does not, and the dispute is whether the off-chain employment or services agreement required something different. A project where vesting is tracked off-chain in a spreadsheet and tokens sit in a founder-controlled wallet presents a wider surface: the founders can argue over who was authorized to move tokens, whether informal amendments were agreed, and whether transfers were legitimate expenses or misappropriation. A treasury held in a multi-signature wallet – common among decentralized projects – adds a layer: the question becomes not only whether a founder breached a vesting term but whether he retains signing authority and, if so, whether a court can compel him to execute (or refrain from executing) specific transactions.
The cross-border reality: crypto projects routinely separate the operating entity (often in a VASP-licensing jurisdiction such as Lithuania or Malta under the MiCA regime, Dubai under VARA or Singapore under MAS), the founders' personal tax residences (driven by individual planning and often in low-tax hubs like the UAE, Switzerland or Portugal), and the exchange or custodian holding the disputed tokens (frequently offshore in the Cayman Islands or BVI, or onshore in a regulated market). A vesting dispute can therefore require parallel enforcement across three or more legal systems, coordinated so that an interim order freezing tokens in one jurisdiction does not become moot because the tokens have already moved through an exchange in a second jurisdiction where notice was slower.
What the vesting documentation must contain
The starting point is the documentation that governs the allocation. In a well-structured token project, founder vesting is addressed in three interlocking instruments: a founder services agreement or employment contract specifying the relationship, the vesting schedule and the termination triggers; a token grant agreement setting out the allocation, the release curve and any clawback or forfeiture mechanics tied to termination; and, where vesting is on-chain, the smart contract itself, which implements the release logic and may include an administrative function allowing the issuer or a designated controller to revoke unvested tokens under defined conditions. The gap between these three layers is where disputes grow: if the services agreement says forfeiture on termination for cause but the token grant is silent and the smart contract has no revoke function, the legal right to forfeit may be unenforceable on-chain.
Contractually, the critical clauses are the vesting commencement date (TGE, the founder's start date, or some earlier reference point such as the private sale close); the cliff and release schedule (a common model is a one-year cliff with monthly or quarterly releases over three to four years thereafter); the acceleration triggers (change of control, acquisition, involuntary termination without cause); and the forfeiture triggers (resignation, termination for cause, breach of restrictive covenants). In our cross-border practice, we routinely see disputes turn on whether "termination for cause" in the services agreement is defined exhaustively or incorporates a general contractual breach standard, and whether a founder's voluntary resignation is treated as forfeiture or merely cessation of further vesting with retention of already-vested tokens.
From a technical enforcement perspective, the documentation should also specify the wallet address to which vested tokens are released, the chain on which the vesting contract operates, and the identity of the administrator authorized to invoke any on-chain revoke or pause function. Without these details, a court order directing the return of tokens becomes difficult to enforce: the order must identify the wallet, the blockchain and the entity (if any) that can execute the reversal, and if those facts are contested or ambiguous, the claimant loses time.
When off-chain agreements conflict with on-chain code
A recurring issue in token vesting disputes is the conflict between what the contract says and what the code does. A founder services agreement may state that unvested tokens are forfeited immediately on termination for cause, but if the vesting contract on-chain continues to release tokens on the original schedule with no administrative override, the forfeiture clause is a legal right without a technical remedy. The claimant must either obtain an order directing the departed founder to return the tokens as they vest (and enforce that order if he does not comply), or seek an injunction requiring the founder to refrain from moving tokens and to transfer them to a court-controlled wallet pending final determination.
Courts in leading common-law jurisdictions have shown a willingness to treat on-chain assets as property subject to proprietary remedies. The England & Wales High Court has granted proprietary injunctions over cryptocurrency where the claimant demonstrates a good arguable case that the defendant holds the assets subject to a trust or acquired them through breach of fiduciary duty or unjust enrichment. In disputes between co-founders, the claim is often framed as breach of the vesting agreement giving rise to a constructive trust over the tokens or, where one founder misused signing authority, as breach of fiduciary duty. The remedy is an order requiring the defendant to transfer the tokens to the claimant's wallet or to a neutral escrow address, combined with an interim injunction preventing further dealings.
Where the vesting contract is genuinely autonomous – the code releases tokens on a time curve with no ability for any party to intervene – the off-chain agreement may still be enforceable, but the remedy is not specific performance (the code cannot be compelled to act differently) but rather an order for payment of the monetary value of the tokens the founder was not entitled to receive, or delivery up of the tokens once they have vested. This distinction matters for limitation periods and for quantification: if the claim sounds in debt or damages rather than proprietary relief, the measure is the value at the date of breach or judgment, not the recovery of the specific tokens.
Multi-signature wallets and control disputes
Treasury assets in a decentralized project are commonly held in a multi-signature wallet, where a transaction requires approval from a threshold of keyholders (e.g., 2-of-3 or 3-of-5). This structure is intended to prevent unilateral control, but it creates a blocking dynamic: a co-founder who holds one key can prevent the remaining founders from executing legitimate treasury operations, and conversely, the remaining founders can freeze out a departing co-founder by changing the wallet configuration if the threshold permits it. The legal question is whether a court can order a founder to sign (or refrain from signing) a specific transaction, and whether non-compliance is contempt.
In principle, a shareholder or services agreement can impose obligations regarding the use of signing authority: a founder may be contractually required to sign off on transactions approved by the board or by a majority of founders, and to surrender the key on termination. Breach of such a clause is a contractual wrong and, if the obligation is framed as an undertaking capable of specific performance, a court may order compliance. Enforcement, however, depends on the court having personal jurisdiction over the founder. If the founder is resident in a jurisdiction that does not recognize the originating court's authority or that treats cryptographic key disclosure as outside the scope of judicial compulsion, the order may be unenforceable in practice.
In a dispute where time is critical – because the departing founder may move treasury funds or because the project requires immediate operational liquidity – the interim remedy is an application for an injunction restraining the founder from using his signing authority pending trial, combined with an order appointing a receiver or administrator with authority to hold the disputed key or to replace the multi-sig configuration if technically feasible. We have seen this structure used in disputes before the DIFC Courts and in England & Wales, where the court treats the key as an instrument of control over property and the injunction as a means of preserving the status quo. The threshold for such relief is a serious question to be tried, evidence of risk of dissipation and a balance of convenience that favours preservation of the treasury.
Freezing tokens at the exchange or contract level
Where tokens have moved to an exchange, the claimant's objective is a freeze before withdrawal or trade. The mechanism is a proprietary injunction combined with, in cross-border cases, a worldwide freezing order directed at the defendant and notification to the exchange as a third party. The exchange is not the target of the order, but it is put on notice that dealing with the specified wallet address may assist a breach, and most regulated exchanges will place an administrative hold pending resolution or court direction. For this to succeed, the claimant must identify the exchange (usually through forensic blockchain analysis or because the defendant disclosed it during earlier correspondence), provide the wallet address or account identifier and move quickly: exchanges in major hubs typically process withdrawal requests within hours, and once assets leave the platform, tracing becomes exponentially harder.
Some stablecoins – notably Tether (USDT) and Circle (USDC) – have contract-level freeze functions that the issuer can invoke. Issuers generally act on a court order from a recognized jurisdiction, on law-enforcement request or in response to an OFAC designation, and the freeze is immediate at the token level across all addresses. In a co-founder dispute, if the contested allocation includes stablecoins and the claimant can demonstrate to a court that the defendant acquired or holds them in breach of trust or vesting terms, the court may issue an order directed at the issuer requiring a freeze. This is not automatic – issuers assess the legal and reputational risk of intervening in a private dispute – but we have seen it succeed where the order comes from a leading common-law court, the claimant's evidence is clear and the quantum is significant.
In a recent recovery matter a token project's treasury was partially drained by a departing co-founder who transferred stablecoins and native tokens to multiple wallets and then to two exchanges. Forensic tracing identified the destination platforms within twelve hours, and the remaining founders obtained an interim proprietary injunction in a major common-law forum. Notice was served on both exchanges; one imposed an immediate hold, and the stablecoins were frozen at contract level following a court direction. The native tokens were traced through a decentralized exchange (DEX) swap, a further bridge and eventual deposit to a custodial wallet, where they were frozen pending final hearing. The entire sequence – from discovery of the transfer to all assets frozen – took under four days. The lesson: speed and accurate on-chain intelligence are dispositive in cross-border crypto disputes.
Choice of forum and enforcement strategy
The choice of forum in a co-founder vesting dispute is driven by the need for speed, the availability of proprietary remedies and the likelihood of recognition in the jurisdictions where the defendant or the assets can be reached. England & Wales is a primary forum for crypto asset recovery due to its established case law treating cryptocurrency as property, its jurisdiction to grant worldwide freezing orders and Norwich Pharmacal disclosure orders, and its willingness to serve proceedings and freezing orders out of the jurisdiction on a defendant with assets or presence in England or, in some cases, where the defendant's only connection is that he holds assets at an exchange operating under English law. The DIFC Courts have shown similar capacity in recent matters involving multi-jurisdictional asset tracing and injunctions in support of foreign proceedings, and the DIFC's position within the UAE makes it a natural choice where the project or one of the founders has a connection to Dubai or Abu Dhabi under the VARA or ADGM regimes.
Where the defendant is personally located in a civil-law jurisdiction that does not recognize English or DIFC judgments without a treaty or reciprocal arrangement, parallel proceedings may be necessary: the claimant obtains a freezing order in the common-law forum where the assets or exchange are situated, and separately pursues recognition or a mirror order in the defendant's home jurisdiction. This is time-intensive and requires local counsel in both forums, but it is often the only route where the defendant has moved to a low-enforcement jurisdiction and holds no assets in a recoverable location.
For projects incorporated in offshore financial centers such as the BVI, Cayman Islands or Mauritius, the company's governing law and the jurisdiction clause in the founder agreements (if present) will determine where proceedings are brought. In our cross-border practice, we regularly advise on structuring founder agreements with an English law or DIFC law governing-law clause and an exclusive or non-exclusive jurisdiction clause in favour of the courts of that system, precisely to ensure that if a dispute arises, the claimant can access the full range of interim remedies without jurisdictional argument. Where no such clause exists, jurisdiction is determined by the defendant's presence, the location of assets or, in some cases, by agreement to submit once the dispute has arisen.
Common mistakes and how to avoid them
The most common mistake in founder vesting arrangements is treating the token allocation as separate from the corporate governance and employment structure. A project that issues tokens to founders before or at TGE without documenting the vesting terms in writing, or that relies on an oral understanding that vesting will follow "standard startup terms," creates an evidential vacuum. When a dispute arises, each party reconstructs the terms from memory, Slack messages and board minutes, and the court is left to infer a vesting schedule from incomplete facts. The result is a slower, more expensive case and a higher risk that the court declines interim relief because the claimant's case is not sufficiently clear.
A second mistake is assuming that a vesting schedule in a token grant agreement is self-executing without considering the on-chain implementation. If the vesting logic is coded into a smart contract with no administrative override, the agreement's forfeiture clause may be unenforceable except through an order directing the defendant to return tokens manually after they vest. This is inefficient and depends on the defendant's compliance. Projects should ensure that vesting contracts include an administrative revoke or pause function controlled by the company (or by a multi-sig that the company controls post-departure), so that forfeiture can be executed on-chain immediately upon a qualifying termination event.
A third mistake is delay in seeking interim relief. Founders often try to resolve disputes through negotiation or arbitration, and by the time they conclude that consensual resolution has failed, the tokens have already moved. The critical window in crypto disputes is the first 24 to 72 hours after the breach is discovered: during that time, the defendant may still hold tokens in a known wallet or on an identified exchange, and a freezing order can be obtained and served before dissipation. Once tokens have been swapped, bridged across chains or moved through a DEX into a privacy protocol or a mixer, recovery becomes materially harder and, in some cases, impossible.
A fourth mistake is failing to address multi-sig key custody in the founder agreements. If a project uses a multi-sig treasury and each founder holds a key, the agreement should state that the key is held in a fiduciary capacity for the benefit of the company, that the founder's authority to use it terminates on cessation of the relationship, and that the founder must either surrender the key or cooperate in a wallet configuration change on departure. Without such a provision, a court order may be required to compel cooperation, and enforcement is uncertain if the founder has left the jurisdiction.
Decision matrix: which remedy for which profile
The choice of remedy depends on the speed required, the location of the defendant and the assets, and whether the primary goal is recovery of specific tokens or monetary compensation. For a fast-moving dispute where tokens are still in a known wallet or on an exchange, the remedy is an interim proprietary injunction and, if cross-border, a worldwide freezing order, obtained on an urgent (often without-notice) application. The timeline is days, and the procedural requirements are an arguable proprietary claim, evidence of risk of dissipation and an undertaking in damages. This route is standard in England & Wales, the DIFC, Hong Kong and Singapore.
For a multi-sig control dispute where no tokens have moved but the departing founder is blocking operations, the remedy is an interim mandatory injunction requiring the founder to sign off on specified transactions or to surrender the key, or alternatively a declaration of the company's rights and an order appointing a receiver to exercise control. The timeline is one to three weeks for an interim hearing, and the threshold is a serious question to be tried and balance of convenience.
For a dispute where tokens have already been dissipated and the claim is for the proceeds or the monetary value, the remedy is a freezing order over the defendant's other assets (which may include fiat accounts, real property or other crypto holdings), combined with a claim for an account of profits, damages or a money judgment. The timeline is longer – months to final judgment – and the procedural posture is a conventional civil claim rather than an emergency application.
For a dispute where the defendant is abroad and outside a reciprocal enforcement jurisdiction, the practical remedy is often a settlement negotiation backed by the threat of a judgment that, while not directly enforceable, will follow the defendant and impair his ability to do business in major markets. This is the least satisfactory outcome, but it reflects the reality that even a strong legal position has limited value if the defendant and the assets are beyond effective reach.
What a pre-dispute structure should look like
Projects planning a token launch with founder allocations should address vesting at three levels: legal, technical and governance. Legally, the founder services or employment agreement should specify the relationship, termination grounds and post-termination obligations (including return of property and surrender of access). The token grant agreement should define the allocation, the vesting schedule, the cliff, acceleration and forfeiture triggers and the governed law and jurisdiction for disputes. Where the founders or the company are in different jurisdictions, the jurisdiction clause should be non-exclusive (allowing a claimant to pursue remedies in the most advantageous forum) and the governing law should be that of a leading common-law or civil-law system with established crypto jurisprudence.
Technically, if vesting is on-chain, the smart contract should include an administrative revoke or pause function controlled by the company (or by a multi-sig that the board controls), so that unvested tokens can be clawed back on-chain if a forfeiture event occurs. If vesting is off-chain, the project should maintain a clear register of allocations and releases, and tokens should be held in a company-controlled wallet until the release date rather than transferred to founders in bulk at TGE.
For treasury management, multi-sig wallets should be paired with a signing authority policy: a board resolution or unanimous founders' agreement specifying the threshold, the circumstances in which a founder must sign or abstain, and the process for replacing a keyholder on departure. The private keys should be held in secure custody (hardware wallets, institutional custody or a key-management service), not on a founder's personal device, and the company should have a protocol for emergency recovery if a founder becomes unavailable or hostile.
From a cross-border tax and banking perspective, the founder agreements should clarify whether token allocations are treated as income (taxed on vesting or release), as capital (taxed on disposal) or as a non-cash benefit subject to withholding, and whether the company or the founder bears the liability. This is particularly important where founders are in different tax jurisdictions: a founder resident in a low-tax hub may argue that tokens vested while resident there and the gain is not taxable in the company's jurisdiction, while the company's tax authority may treat the allocation as employment income subject to withholding. Aligning founder residency with the holding structure and the anticipated exit plan – whether a token sale, equity acquisition or eventual public listing – avoids the outcome where the founders' personal tax positions conflict with the company's reporting obligations or where a vesting dispute is complicated by competing tax claims.
Objection handler: a common assumption
A common assumption among founders is that relocating personally – for instance, moving to Dubai or another low-tax jurisdiction – is sufficient to change the group's tax position and that corporate structure can be addressed later. In reality, the interaction between personal tax residency and the entity's tax residence, the source of income and the location of the management and control functions determines the overall tax treatment, and these elements must be aligned from the outset. If a founder relocates but the company remains tax-resident in a high-tax jurisdiction, the company may still have withholding obligations on the founder's token allocation, and the founder may remain liable in his former jurisdiction if he has not broken tax residence cleanly. If the company subsequently changes domicile, the redomiciliation itself may trigger exit tax or create a gap period where the entity is dual-resident. The correct approach is to plan the founder residency and the holding structure together, taking into account where the entity will be licensed (if it is a VASP or token issuer), where it will bank, where the majority of operations and decision-making occur, and where the founders intend to be for the vesting period and beyond. This is a single exercise in cross-border structuring, not a series of disconnected decisions, and it should occur before the TGE, not in response to a dispute or a tax assessment two years later.
For a scoped assessment of a founder token structure or recovery options in a live dispute, contact OBOLUS at info@oboluslaw.com.
Why speed determines outcome in token disputes
The defining feature of digital-asset disputes is that the limitation period is effectively set by the blockchain, not by statute. In a traditional corporate dispute, a claimant has years to bring a claim, and assets – real property, bank accounts, share certificates – remain static and traceable throughout. In a token dispute, the defendant can move assets across wallets, chains and jurisdictions in minutes, and once tokens enter a decentralized exchange, a privacy protocol or are converted into an untraceable asset, the claim for specific recovery is lost. The claimant is left with a damages claim against a defendant who may be judgment-proof or located in a non-enforcement jurisdiction. The practical consequence is that disputes over token vesting, treasury misappropriation or key control must be treated as urgent from the moment the breach is discovered, and the legal response – forensic tracing, application for interim relief, service on exchanges or issuers – must be mobilized within a 48-to-72-hour window.
This does not mean every founder dispute requires emergency court applications. Where the parties are negotiating in good faith, where tokens have not yet vested or where the allocation is locked in a transparently audited vesting contract with no risk of early release, a measured approach is appropriate. But where a departing founder holds liquid tokens, controls a signing key or has already initiated transfers inconsistent with the vesting schedule, delay is dispositive. The cases that succeed in recovering significant digital assets are those where the claimant's advisors moved within hours of the breach, not days or weeks.
The role of forensic blockchain intelligence
Effective recovery in a token vesting dispute depends on accurate on-chain tracing. The claimant must identify the wallet addresses to which the disputed tokens were sent, track subsequent movements through exchanges, bridges or DeFi protocols, and determine whether the tokens are still held in a location where they can be frozen or whether they have been converted into a different asset or dissipated. This requires forensic blockchain analysis, typically provided by a specialist firm such as Chainalysis, Elliptic or TRM Labs (no engagement or affiliation; capability framing only).
A forensic report serves multiple functions: it provides the evidential foundation for the proprietary claim (demonstrating that the tokens in the defendant's wallet are traceable to the claimant's treasury or vesting allocation), it identifies the exchanges or custodians where the tokens currently reside (enabling the claimant to serve notice and request a hold), and it may reveal other assets that can be joined to a freezing order if the primary tokens have been sold. Courts in England & Wales, the DIFC and Singapore routinely admit blockchain forensic evidence in support of urgent applications, provided the report is prepared by a credible expert and explains the tracing methodology in terms a judge without technical background can follow.
For the purpose of obtaining a freezing order, the claimant does not need to prove the case at the interim stage – the threshold is a good arguable case and risk of dissipation – but the forensic evidence must be clear enough to demonstrate a real prospect of success and to show that the assets the claimant seeks to freeze are indeed the product of the alleged breach. A report that concludes "tokens were sent from Wallet A to Wallet B, and Wallet B is associated with Defendant" is usually sufficient. A report that merely states "tokens left the treasury" without tracing the destination is not.
When arbitration is the agreed forum
Some founder agreements include an arbitration clause, either institutional (ICC, LCIA, SIAC, DIFC-LCIA) or ad hoc. Arbitration offers confidentiality and the advantage that an award is enforceable across borders under the New York Convention, but it creates a tension in urgent crypto disputes: arbitral tribunals cannot issue freezing orders or proprietary injunctions that bind third parties such as exchanges, and the time to constitute a tribunal – often several weeks – is longer than the time it takes for tokens to move. The solution used in cross-border practice is to apply to a national court for interim relief in support of arbitration under the applicable arbitration statute (for example, section 44 of the English Arbitration Act 1996, or equivalent provisions in Singapore and Hong Kong). The court grants a freezing order or proprietary injunction on an urgent basis, the substantive dispute proceeds to arbitration, and the interim order is discharged or continued depending on the tribunal's later directions.
This hybrid approach works where the arbitration clause permits parties to seek interim relief from a court, or where the clause is silent and the governing arbitration law allows it. Where the clause purports to be exclusive of court remedies, or where the defendant challenges the court's jurisdiction on the basis that the matter is subject to arbitration, the claimant may face delay while the jurisdictional issue is resolved. For this reason, arbitration clauses in founder agreements involving digital assets should be drafted to expressly preserve the parties' right to seek interim and conservatory measures from any court of competent jurisdiction, without waiving the agreement to arbitrate the substantive dispute.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. In cross-border disputes involving token allocations, treasury misappropriation and founder control, we structure licensing, banking and tax as one mandate rather than three disconnected workstreams, so that a recovery strategy, a licence application and the founders' personal tax planning are aligned from the outset rather than reconciled after a problem emerges. To discuss your situation, contact info@oboluslaw.com.
Related at OBOLUS
- Disputes & Asset Recovery for Digital-Asset Businesses – the firm's litigation and recovery practice across injunctive relief, tracing and enforcement
- Acquiring a Licensed VASP: Change-of-Control Approvals – regulatory clearance when a token project or fund acquires a licensed entity or changes its shareholder structure
- Stablecoin Freeze Request in Turkey – jurisdictional procedure for freezing USDT or USDC at contract level in a Turkish fraud matter
FAQ
Can stolen crypto actually be recovered?
Yes, if action is taken within the first 24 to 72 hours. Where tokens remain in an identified wallet or on an exchange, a court in a leading forum such as England & Wales or the DIFC can issue a proprietary injunction freezing the assets. Stablecoins such as USDT and USDC can be frozen at contract level by the issuer following a court order. Once tokens are moved through decentralized exchanges, bridges or privacy protocols, recovery becomes materially harder, but even dissipated assets may be traceable to other holdings that can be frozen. The critical factor is speed.
How fast must I act after a digital-asset theft?
Immediately. The effective limitation period in a crypto dispute is set by the blockchain, not by statute: defendants can move tokens across wallets, chains and jurisdictions within minutes. A successful recovery typically depends on forensic tracing and an urgent court application within 48 to 72 hours of discovering the breach. Delay of even a few days can render the assets untraceable or allow withdrawal from an exchange before a freeze order is served.
Can a court freeze assets held on an exchange?
Yes. A proprietary injunction or worldwide freezing order can be served on an exchange as a third party, and most regulated platforms will place an administrative hold on the specified wallet or account pending court resolution or further direction. The claimant must provide the exchange's identity and the relevant wallet address or account identifier, typically obtained through forensic blockchain analysis. Exchanges in major hubs generally respond within hours to a court order from a recognized jurisdiction.
By Glen Sorensen, Disputes & Recovery Analyst – specializing in cross-border asset tracing, injunctive relief and enforcement in digital-asset disputes across common-law and offshore forums.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.