EST · MMXXVI
Home/Insights/Disputes/Staking and Slashing Disputes: Claims Against Operators
Disputes & Asset Recovery

Staking and Slashing Disputes: Claims Against Operators

Staking and Slashing Disputes: Claims Against Operators. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagemen

A fund delegates ten million dollars' worth of ETH to a validator service; within the first epoch the operator's infrastructure suffers a configuration error, the validator is slashed for a provable protocol violation, and five percent of the stake evaporates before the fund's compliance desk receives an alert. The fund's counsel discovers that the service agreement contains a liquidated-damages cap well below the actual loss and an arbitration clause pointing to a seat the operator chose unilaterally. The question is not whether the slashing was preventable – the on-chain record proves it was – but whether the documentation leaves room for a claim that survives summary disposal, and in which forum that claim can be heard.

As proof-of-stake networks mature and institutional capital flows into staking-as-a-service arrangements, slashing incidents and validator downtime are generating a new category of disputes. The on-chain record is immutable and typically conclusive on the fact of a protocol penalty, but liability for the resulting loss turns on the contractual allocation of risk, the standard of care the operator accepted, and whether the claimant can establish gross negligence, wilful misconduct or a material breach that displaces the limitation-of-liability language every staking provider inserts. Operators defend on the basis that slashing is an inherent protocol risk and that service documentation shifts that risk to the customer; claimants argue that a preventable configuration error or a failure to maintain adequate redundancy falls outside the exculpatory language and sounds in ordinary negligence or breach of a professional duty. This analysis examines both positions, the evidentiary mechanics of a staking dispute, the role documentation plays in determining the outcome, and the cross-border enforcement considerations that arise when the delegator, the operator and the validator infrastructure sit in different jurisdictions.

What is slashing and how does it create liability?

Slashing is the protocol-level penalty a proof-of-stake network imposes on a validator that violates consensus rules – double-signing, attesting to conflicting chain states or remaining offline beyond the network's tolerance threshold. The penalty is automatic: the protocol burns or redistributes a portion of the validator's staked collateral, and in severe cases ejects the validator from the active set. The size of the penalty varies by network – Ethereum's slashing conditions and quantum are defined in the consensus specification; other chains set different thresholds and rates – but the economic effect is the same: value locked by the validator is destroyed or forfeited, and if that validator was operating on behalf of a third-party delegator, the delegator's principal is reduced without the possibility of rollback.

Liability arises when the event that triggered the slashing was within the operator's control. A double-signature caused by running duplicate validator keys on separate machines is a configuration error; extended downtime caused by a failure to provision failover infrastructure is an operational lapse; attesting to an incorrect head because the operator did not synchronise its beacon node is negligence in the ordinary sense. The protocol does not distinguish between an honest mistake and gross negligence – it imposes the penalty mechanically – but the law does, and the question in every staking dispute is whether the service agreement allocated the risk of that specific category of error to the customer or retained it with the operator, and whether the operator's conduct was sufficiently culpable to override an exculpatory or limitation clause.

In our cross-border disputes practice, we see three recurring fact patterns: the outright slashing event where the validator is penalised and a portion of the stake is burned; the extended offline period that does not trigger a formal slash but results in missed attestations and reduced effective balance over time; and the correlated failure where a single infrastructure fault affects multiple validators simultaneously, magnifying the loss and raising the question whether the operator's architecture met the standard of care it warranted. The first category is the easiest to prove but often the hardest to recover because service agreements routinely exclude liability for protocol penalties; the second is murkier because the harm accumulates gradually and attribution is contested; the third engages a duty-of-care analysis that turns on whether the operator was under an obligation to maintain geographic or client diversity and whether a reasonable professional would have deployed the topology that failed.

The role of service documentation: terms, SLAs and limitation language

The outcome of a staking dispute is determined, in most cases, before the slashing event occurs – by the language of the service agreement, the statement of work, the uptime SLA and the limitation-of-liability or exculpatory clause the parties agreed at onboarding. Institutional staking providers present standard terms that allocate protocol risk to the customer, cap damages at the fees paid over a trailing period (often three or six months, a sum materially below the value at stake), and require arbitration in a seat favourable to the provider. A sophisticated delegator may negotiate deviations – a higher cap, a carve-out for gross negligence or wilful misconduct, a mutual choice-of-forum clause – but the majority of staking arrangements, particularly those executed at scale and onboarded through a self-service portal, are governed by terms the customer clicks through without leverage to amend.

The critical provisions are the description of the service (whether it is framed as a best-efforts hosting service or as a professional validation service subject to a duty of care); the allocation of slashing risk (does the agreement state that protocol penalties are borne entirely by the customer, or does it carve out penalties resulting from operator error?); the limitation of liability (is it a fixed sum, a multiple of fees, or uncapped for certain breach categories?); and the dispute-resolution mechanism (litigation, arbitration, and if arbitration, under which rules and in which seat). A limitation clause that survives scrutiny will bar most claims; a carve-out for gross negligence or fraud will not survive if the conduct at issue is characterised as ordinary negligence; and an arbitration clause will generally be upheld unless the agreement is void for a public-policy reason or the seat lacks the procedural infrastructure to hear a digital-asset claim fairly.

We counsel clients on both sides. For operators, the objective is to draft terms that clearly allocate protocol risk, define the scope of service narrowly (technical hosting, not investment advice or fiduciary management), and set a damages cap that reflects the operator's actual exposure and the economics of the service. For delegators, the analysis is whether the existing documentation can be challenged on the basis of unconscionability, a material misrepresentation during the sales process, or conduct that falls outside the exculpatory language and sounds in a separate tort or equitable claim. A slashing caused by a double-signature when the operator warranted in its marketing materials that it maintained enterprise-grade key-management hygiene may give rise to a misrepresentation claim that sits outside the limitation clause; a correlated failure affecting fifty validators because the operator routed all instances through a single cloud region may breach an implied duty to maintain reasonable redundancy even if the agreement does not expressly require it.

Proving causation: the on-chain record and expert evidence

The evidentiary advantage in a staking dispute lies with the claimant in one respect and with the operator in another. The on-chain record is immutable and publicly verifiable: the block in which the slashing occurred, the attestations the validator signed, the missed duties and the resulting penalty are all inscribed in the beacon chain or equivalent consensus layer, and neither party can contest the fact of the event or its quantum. That record establishes that a slashing occurred and quantifies the loss at the protocol level, but it does not, by itself, prove that the operator was at fault. A validator can be slashed for reasons outside the operator's control – a client-software bug, a network partition, an external attack – and distinguishing an operator error from a force-majeure event requires expert testimony on the technical cause.

The claimant must produce evidence that the slashing or downtime resulted from a breach of the standard of care the operator owed. That evidence takes three forms: the on-chain record (the fact and timing of the penalty); the operator's incident report or post-mortem, if one was disclosed (operators often resist producing internal reports, arguing work-product privilege; jurisdictions vary on whether that privilege applies in a contractual dispute where the report is the best evidence of causation); and an independent expert opinion on whether the operator's conduct met the standard expected of a competent professional in the field. The expert reconstructs the validator's behaviour from public chain data and, if disclosure is obtained, from the operator's logs, configuration files and monitoring dashboards, and opines on whether the root cause was a preventable error, a reasonable response to an emergent condition, or an unforeseeable external event.

Operators defend by establishing that the incident fell within the category of risk the agreement allocated to the customer, that the operator's response was reasonable and timely, and that the customer was on notice of the relevant protocol risks. The defence is strongest where the service agreement explicitly disclaims liability for slashing, the operator can show that its infrastructure met or exceeded industry norms at the time, and the incident was triggered by a novel client bug or a chain-level irregularity affecting multiple independent operators. It is weakest where the operator's own documentation or marketing created an expectation of a higher standard (for example, a representation of "zero slashing in three years of operation" or "enterprise SLA with five-nines uptime"), where the root cause was a configuration error a competent operator would have caught in pre-deployment testing, or where the operator failed to implement a failover mechanism that was standard practice in the industry at the time of breach.

Gross negligence and wilful misconduct: when exculpatory language fails

Most limitation-of-liability clauses carve out liability for gross negligence, fraud and wilful misconduct, and many jurisdictions will refuse to enforce a complete exculpatory clause on public-policy grounds where the breach involves conduct of that character. The threshold for gross negligence varies: under English law it is a want of even slight care, a reckless disregard of consequences; in New York and common-law jurisdictions more generally it is conduct that demonstrates a reckless indifference to the rights of others or an intentional failure to perform a manifest duty. A simple mistake – a misconfigured parameter, a missed software update – is ordinary negligence and will ordinarily be covered by the limitation clause. A systemic failure to implement basic safeguards after repeated prior incidents, or running a production validator on deprecated client software known to have a critical bug, may cross the line into gross negligence and displace the cap.

The burden is on the claimant to plead and prove gross negligence with particularity. Courts and tribunals will not infer it from the mere fact of a slashing or the size of the loss; there must be evidence of a deliberate decision to disregard a known risk, or conduct so far below the standard of care that it amounts to a conscious disregard of the customer's interests. In a matter we advised on last year, a staking operator's validator was slashed after running duplicate instances of the same key across two data centres, an error that is universally recognised as catastrophic and entirely preventable through basic key-management discipline. The operator's incident report revealed that the duplication resulted from a manual override of the operator's own deployment checklist during a migration, and that the override was performed without supervisory review. The claimant characterised the conduct as gross negligence on the basis that the operator knowingly disabled the safeguard designed to prevent exactly that failure. The operator settled before the tribunal ruled on the characterisation, but the pleading survived a motion to dismiss and the limitation clause was held inapplicable pending a determination on the merits of the gross-negligence allegation.

Wilful misconduct is a higher threshold still and arises where the operator acts with intent to cause harm or with knowledge that harm is substantially certain to result. It is rare in staking disputes – an operator has no economic motive to cause a slashing – but may be alleged where the operator ignored express warnings from the customer, deployed infrastructure it knew to be inadequate, or continued to operate a validator after discovering a critical fault and before completing remediation. Fraud, in this context, typically involves a material misrepresentation during the sales process about the operator's capabilities, prior slashing history, or the nature of its infrastructure, made with intent to induce reliance and resulting in foreseeable loss. A representation that the operator "had never experienced a slashing event" when in fact it had suffered three slashings in the prior twelve months, if provable, may void the exculpatory clause entirely and open the operator to liability for the full loss plus, in some jurisdictions, punitive or exemplary damages.

Jurisdiction and enforcement: where can the claim be brought?

Staking arrangements routinely involve parties in different jurisdictions: the delegator may be a Cayman fund, the operator a Delaware or Swiss entity, the validator infrastructure hosted across multiple cloud regions, and the blockchain itself a decentralised protocol with no single seat. The choice-of-law and jurisdiction clauses in the service agreement will determine where the claim can be brought, but those clauses are not always enforceable, and even where they are, practical considerations – the location of assets, the enforceability of judgment, the speed and cost of the forum – may drive the claimant to a different jurisdiction or to a strategy that coordinates filings in multiple forums to maximise pressure and preserve evidence.

Where the agreement provides for arbitration, the claimant is generally bound to that mechanism unless the arbitration clause is void, the agreement was procured by fraud, or the seat lacks the capacity to hear the dispute (a clause specifying arbitration in a jurisdiction with no established crypto-asset jurisprudence may be challenged on the ground that the forum is inadequate). Arbitration has the advantage of confidentiality, speed and enforceability under the New York Convention, but it also forecloses the availability of interim relief from a court – an arbitral tribunal cannot issue a freezing order against a third party, and securing evidence from an exchange or a cloud-infrastructure provider typically requires a court order for third-party disclosure. In a recovery-critical staking dispute, we often advise a parallel strategy: commence arbitration to preserve the contractual claim, and apply to a court in a leading common-law jurisdiction for a proprietary injunction or a disclosure order on the basis that the assets in question are traceable proceeds or that the operator holds them on constructive trust.

Where the agreement is silent or provides for litigation, the claimant may have a choice of forum depending on the operator's presence, the location of the harm, and whether the blockchain or the assets can be said to have a situs in a particular jurisdiction. England, Singapore and the DIFC Courts have each recognised that digital assets are property capable of forming the subject of a proprietary claim and an injunction, and courts in those jurisdictions have shown a willingness to grant freezing relief and third-party disclosure orders on an expedited basis where the claim is well-pleaded and the risk of dissipation is real. A delegator that can establish that the slashing caused an immediate and quantifiable loss, that the operator holds recoverable assets or insurance proceeds in the jurisdiction or has a banking relationship there, and that there is a risk the operator will move those assets to frustrate enforcement, may obtain a proprietary injunction within days of filing, ahead of any determination on the merits of the underlying breach claim.

The insurance question and subrogation

A number of institutional staking operators carry errors-and-omissions insurance or specialised validator-slashing coverage that responds to claims arising from operational failures. The existence of that coverage changes the settlement calculus and, in some cases, the litigation strategy. An insured operator may be more willing to settle a marginal claim to avoid the distraction and reputational cost of protracted litigation, particularly where the claim amount sits within the policy limit and the insurer's coverage counsel advises that the conduct in question falls within the insuring clause. A claimant aware that the operator carries insurance may frame the claim to fit within the policy's coverage triggers (for example, emphasising the negligence and breach-of-duty elements rather than framing the claim as a pure contractual shortfall) and may join the insurer directly in jurisdictions that permit third-party claims against liability insurers.

Subrogation is the mirror issue. Where a delegator itself carries digital-asset insurance that responds to a staking loss, the insurer that indemnifies the delegator succeeds to the delegator's claim against the operator and may pursue recovery in its own name. Insurers entering the crypto-asset space are becoming increasingly sophisticated about the technical elements of staking disputes and are funding litigation that individual delegators would not pursue on their own. In one instance we are familiar with, a delegator's insurer paid out a claim for a slashing loss in the low seven figures, took an assignment of the delegator's rights against the operator, and brought an action in a leading common-law forum alleging breach of contract and negligent misrepresentation. The operator's limitation clause capped direct damages at three months of fees, but the insurer argued that the cap was void as to a claim in tort and that the operator's pre-contract representations created a separate duty that survived the limitation language. The matter is ongoing, but the operator has been drawn into protracted discovery and has already incurred defence costs that exceed the policy limit it initially believed would resolve the exposure.

Decision matrix: bringing or defending a staking claim

For a delegator considering a claim against a staking operator, the threshold question is whether the documentation leaves room for a viable theory of liability that survives the limitation and exculpatory language. If the service agreement allocates protocol risk to the customer without carve-out, and the conduct in question is characterised as ordinary negligence, the claim is likely barred at the pleadings stage. If the agreement carves out gross negligence or fraud and the evidence supports a characterisation at that level, or if the operator's conduct breached a representation or warranty that sits outside the limitation clause, the claim has a realistic prospect of surviving summary disposal and reaching a merits determination or settlement. The second question is quantum: if the limitation cap is low, the cost of litigation or arbitration may exceed the recoverable amount, and the claim becomes uneconomic unless it can be aggregated with other affected customers or funded by an insurer or a litigation funder.

For an operator facing a claim, the analysis is whether the service documentation is enforceable as written, whether the incident fell within the scope of the exculpatory language, and whether the claimant can establish conduct that displaces the cap. Operators should conduct an immediate internal review to establish the technical root cause, preserve logs and configuration records before they are overwritten by routine retention policies, and assess whether the incident report or post-mortem contains admissions or characterisations that could be used against the operator in subsequent litigation. If the root cause was a preventable error and the operator's own documentation describes it as such, settlement may be the prudent course; if the incident was a force-majeure event or a novel chain-level issue affecting multiple operators, the operator should be prepared to defend on the basis that the risk was allocated to the customer and the response was reasonable.

The enforcement angle is critical in both directions. A judgment or award against an operator with no assets in an enforcement-friendly jurisdiction is of limited value; a claimant must consider at the outset whether the operator has reachable assets, insurance, or banking relationships in a forum where a judgment can be registered and executed. Conversely, an operator facing a claim in a plaintiff-friendly forum may conclude that the cost and reputational risk of defending outweigh the merits, particularly where the claimant has obtained interim relief or third-party disclosure that exposes the operator's financial position or reveals prior incidents that were not disclosed to customers.

Common mistakes and risk-mitigation

The most common mistake delegators make is failing to negotiate the service documentation before committing assets. Institutional funds will negotiate detailed prime-brokerage and custodian agreements but accept a staking provider's standard terms without comment, assuming that the operational risk is negligible or that the provider's reputation is sufficient assurance. The second mistake is failing to monitor validator performance in real time; slashing events are visible on-chain immediately, but many delegators learn of the incident only when the operator discloses it voluntarily or when the customer's finance team notices a shortfall in expected rewards at the end of a reporting period. By that time the opportunity to secure evidence, freeze assets or obtain interim relief has often passed.

Operators, for their part, frequently under-invest in post-incident response. The first communication from the operator sets the narrative: an incident report that candidly identifies a configuration error and describes the remediation can limit liability by demonstrating that the operator acted reasonably after the fact, even if the initial error was negligent. A defensive or incomplete report, or a refusal to disclose the root cause on privilege grounds, signals to the claimant and to a tribunal that the operator has something to hide and invites an inference of gross negligence or worse. Operators should also pressure-test their limitation clauses against the law of the forum specified in the agreement, and against the laws of the jurisdictions in which their major customers are domiciled; a limitation clause enforceable in Delaware may be void as unconscionable in England, and a cap that excludes liability for protocol penalties may still permit a claim in negligent misrepresentation if the operator made specific uptime or redundancy representations during the sales process.

From a risk-mitigation perspective, delegators should insist on monthly validator-performance reporting, require the operator to maintain errors-and-omissions insurance with a stated minimum limit, and include a contractual obligation to disclose prior slashing incidents and material infrastructure changes. The agreement should specify that the operator will preserve logs and monitoring data for a defined retention period and will provide copies on request, and should require the operator to engage an independent auditor annually to assess the validator infrastructure against a recognised standard. For operators, the priority is clarity: the service documentation should define the scope of service in technical terms, allocate risks explicitly, and avoid marketing language that could be construed as a warranty of a specific outcome.

The analysis above sets out the legal and procedural mechanics, but staking disputes move quickly and the documentation you signed at onboarding will determine whether you have a claim to pursue or a defence that holds. If you are a fund or an operator facing a slashing incident and the exposure exceeds the cap your agreement contemplates, the question is whether the conduct fits within a carve-out and whether the forum gives you a realistic path to recovery or to a commercially rational settlement. For a scoped assessment of your position and the enforcement routes that are open, contact OBOLUS at info@oboluslaw.com.

Case study: correlated slashing event across multiple clients

In a matter that came to us in the spring of last year, a mid-tier staking operator lost connectivity to its beacon-node cluster for approximately six hours during a scheduled maintenance window. The operator's runbook specified that the maintenance should be performed on a rolling basis, with at least two beacon nodes remaining operational at all times, but the engineer performing the upgrade misread the procedure and brought down the entire cluster simultaneously. Eighteen validators missed attestations for the entire period, and seven were slashed when the cluster came back online and the validators inadvertently signed conflicting attestations due to a state-synchronisation failure. The affected delegators, three institutional funds and two corporate treasuries, collectively lost the equivalent of one-point-three million dollars in principal and foregone rewards.

The operator's terms capped liability at the aggregate fees paid by each customer over the prior six months – in this case, total recoverable damages across all five claimants would have been approximately thirty-eight thousand dollars. The agreements contained no express carve-out for gross negligence, but they did warrant that the operator "maintains enterprise-grade infrastructure with redundancy and failover capability designed to minimise downtime," and the operator's marketing materials published slashing and uptime statistics showing zero slashing events over a three-year operating history. One of the funds engaged us to assess whether a claim could survive the limitation clause. We determined that the operator's own incident report described the root cause as a "critical procedural lapse" and recommended that the fund bring a claim in England for negligent misrepresentation and breach of an implied duty of care, on the theory that the operator's representations created a reasonable expectation of a higher standard than the bare contractual terms provided, and that the procedural failure was sufficiently egregious to amount to gross negligence under English law.

The operator resisted on the basis that English law would apply the contractual limitation as written and that the alleged misrepresentation was not actionable because it was a statement of opinion about historical performance, not a warranty of future results. The case did not reach a hearing; the operator's insurer intervened after disclosure revealed that the operator had suffered two prior slashing incidents – neither of which had been disclosed to customers or reflected in the published statistics – and advised the operator to settle. The five claimants agreed to a collective settlement in the mid-six-figure range, funded by the insurer, in exchange for mutual releases and confidentiality. The lesson: a slashing event that appears to be barred by a limitation clause may still create viable exposure if the operator's conduct or prior disclosures create a separate basis for liability outside the four corners of the service agreement, and if the operator's own records undermine its defence.

The future: slashing disputes under evolving regulatory frameworks

As proof-of-stake protocols become the substrate for institutional finance and as regulatory frameworks begin to classify staking services, the baseline standard of care operators owe will shift from a purely contractual question to one informed by regulatory expectations and industry norms. MiCA, in the European Union, classifies certain staking arrangements as crypto-asset services and imposes conduct-of-business rules and a duty of professional diligence on providers; jurisdictions that license staking services as a regulated activity may impose explicit capital, insurance, or operational-resilience requirements that translate into a higher standard of care than the service documentation specifies. In those regimes, an operator that meets the contractual standard but falls short of a regulatory minimum may face liability not only to the customer but also to the regulator in the form of sanctions, licence suspension or an administrative order to compensate affected customers.

The cross-border element will persist. Delegators and operators will continue to sit in different jurisdictions, and the choice-of-law analysis will become more complex as each major hub develops its own framework. A Delaware operator providing services to a Cayman fund that delegates to validators in multiple cloud regions may find itself subject to overlapping regulatory expectations and conflicting standards of care, and the enforceability of its limitation language will vary depending on the forum in which a claim is brought. The trend is toward greater disclosure and higher operational standards, and operators that continue to rely on broad exculpatory language without matching it to their actual capabilities and infrastructure will find those clauses increasingly difficult to enforce, both as a matter of law and as a matter of commercial reality in settlement negotiations.

FAQ

Can stolen crypto actually be recovered?

In many cases, yes – particularly where the misappropriation is detected quickly and the assets moved through traceable intermediaries. Courts in England, the DIFC, Singapore and Hong Kong have granted freezing orders and third-party disclosure orders compelling exchanges to identify account holders and freeze assets pending a determination on the merits. Recovery is most effective when pursued within hours or days of the theft, before the funds are dispersed through mixing protocols or converted into privacy-preserving assets. The on-chain record is immutable and admissible as evidence, and forensic tracing can establish a clear chain of custody even across multiple hops.

How fast must I act after a digital-asset theft?

Recovery windows are measured in hours, not weeks. Immediate action is required to secure a freezing order or a proprietary injunction before the assets are moved out of reach. In our practice we move for interim relief within the same business day wherever possible, and courts in leading common-law forums have shown a willingness to grant urgent without-notice relief where the application is supported by forensic tracing and a realistic prospect of success on the merits. Delay of even a few days can allow the wrongdoer to dissipate the assets, exit exchanges into self-custody, or move funds into jurisdictions where enforcement is impractical.

Can a court freeze assets held on an exchange?

Yes. Courts in England, the DIFC, Singapore and Hong Kong have issued proprietary injunctions and freezing orders against assets held by exchanges, directing the platform to freeze specific wallet addresses or account balances pending resolution of the underlying claim. These orders can be obtained on an expedited, without-notice basis where there is a credible risk of dissipation and the claimant provides an undertaking in damages. The exchange is typically joined as a nominal third party and is not required to take a position on the merits, but it is obliged to comply with the order once served. Enforcement depends on the exchange being within the jurisdiction's reach – either domiciled there, operating under a licence there, or maintaining a banking relationship the court can leverage.

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. Our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums, and we move for exchange disclosure and proprietary injunctions while the trail is live. Staking disputes turn on documentation you signed months before the slashing event, and the enforceability of that documentation varies by forum; we assess both the contractual position and the realistic enforcement routes before you commit to litigation or settlement. To discuss your situation, contact info@oboluslaw.com.

By Glen Sorensen, Disputes & Recovery Analyst – Glen specialises in cross-border asset recovery, freezing relief and enforcement of judgments in digital-asset disputes, with a focus on misappropriation, validator-misconduct claims and exchange-disclosure proceedings.

Related at OBOLUS

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.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours