EST · MMXXVI
Home/Practices/Restaking and Liquid Staking: Legal Counsel for Protocols and Operators
DeFi, Tokenization & Smart-Contract Law

Restaking and Liquid Staking: Legal Counsel for Protocols and Operators

Restaking and Liquid Staking: Legal Counsel for Protocols and Operators. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fix

A protocol launches a liquid-staking derivative (LSD) that compounds yield across three proof-of-stake networks, then offers the receipt token as collateral in a restaking layer that secures an oracle network. On paper, each step unbundles risk and liquidity. In practice, the legal question is whether the cascade of yield obligations and the discretion exercised by node operators convert the instrument into a regulated investment contract – and who carries liability when a slashing event propagates through the stack. Restaking and liquid-staking architectures sit at the frontier of decentralised finance: they are capital-efficient, cross-chain and operationally complex, and every element – the token, the validator relationship, the slashing allocation, the disclosure to stakers – invites regulatory scrutiny under securities, commodities and payments frameworks across jurisdictions.

OBOLUS advises protocols, node operators and infrastructure funds on the legal structuring of restaking and liquid-staking products. We map the instrument against securities and commodities tests in the jurisdictions where users sit, draft operator agreements that allocate slashing and cascade risk, assess disclosure obligations for the yield mechanism and the validator set, and structure the entity and governance to defensibly decentralise control. Restaking and liquid staking are the whole of this analysis. This page sets out the legal perimeter, the classification risks, the operator framework and the path to a defensible launch.

What is restaking and liquid staking

Restaking allows a staked asset – typically a proof-of-stake token already locked to secure one network – to secure additional protocols simultaneously. A user stakes ETH to validate Ethereum; that staked position is then re-pledged (restaked) to secure an oracle, a bridge or a data-availability layer, often through a middleware protocol that aggregates security demand. The restaker earns additional yield; the secured protocol inherits economic security without bootstrapping a new validator set. Liquid staking issues a tradable receipt token (an LSD) representing the underlying staked position, allowing the holder to use the derivative in DeFi while the principal remains locked in the validator. When restaking is applied to an LSD, the compounding effect – yield from the base-layer staking, yield from the restaking rewards and any yield from deploying the LSD in lending or liquidity pools – creates a multi-tier structure where slashing risk, validator discretion and yield attribution span multiple smart contracts and jurisdictions.

The technical elegance of restaking masks a jurisdictional question: whether the receipt token or the restaking position qualifies as a security under the substance-of-rights test that most regulators apply. If the holder reasonably expects profit derived primarily from the efforts of the protocol team or the validator operator, the instrument may meet the definition of an investment contract in the United States, a collective-investment scheme in the United Kingdom or a transferable security under MiCA in the European Union. The analysis turns on control, discretion and the marketing of yield – not on whether the whitepaper calls the token "utility."

Securities classification of the restaking instrument

The first question in a restaking or liquid-staking launch is whether the instrument is a security. In the United States, the Howey test asks: is there an investment of money in a common enterprise with an expectation of profit derived substantially from the efforts of others? A liquid-staking token that automatically compounds validator rewards and is marketed on projected annual percentage yield meets the first three prongs trivially. The fourth – efforts of others – is satisfied if the protocol or the operator exercises meaningful discretion over validator selection, slashing-penalty distribution, upgrade paths or reward reinvestment. Decentralisation is not a binary switch: a protocol governed by token-weighted voting but where a foundation controls the validator whitelist, the slashing-insurance pool or the fee structure retains sufficient centralised control that the SEC and other regulators may classify the instrument as a security.

Under MiCA, which took full effect across the European Union in December 2024, a crypto-asset that confers rights similar to shares, bonds or units in a collective-investment undertaking is a transferable security and falls outside MiCA into the existing securities directives. An asset-referenced token (ART) or an e-money token (EMT) under MiCA must be backed by a reserve; a restaking derivative that represents a claim on staking rewards rather than a redeemable reserve does not fit the ART or EMT definitions and is instead assessed as a transferable security if the holder's return depends on the protocol's or operator's performance. National competent authorities in member states have taken divergent initial positions on staking derivatives; operators launching into the EU market pressure-test the instrument against both the MiCA framework and the local securities authority's interpretation before go-live.

In our cross-border practice, protocols building restaking or liquid-staking products routinely structure to move discretion out of the issuer and into an on-chain governance process or a distributed validator set. Where that shift is genuine – governance proposals pass by token-holder vote without a controlling block, validator selection is permissionless or follows objective on-chain criteria, slashing penalties are allocated by immutable smart-contract logic – the classification risk decreases. Where the shift is cosmetic, the risk remains. A securities lawyer's first task is to map where discretion actually sits, not where the documentation says it sits.

Operator duties and validator relationships

A restaking protocol aggregates security: it takes in staked or restaked positions and allocates them to validators who secure multiple downstream networks. The relationship between the protocol, the node operator (the entity running the validator infrastructure) and the end staker determines who carries what duty. If the operator has discretion over which networks to secure, how to allocate slashing insurance or when to exit a position, that operator may owe a fiduciary or quasi-fiduciary duty to stakers – particularly in common-law jurisdictions where a party exercising discretion over another's property on trust-like terms incurs equitable obligations. The duty is not extinguished by a click-through disclaimer.

In practice, the operator agreement – the contract between the protocol (or a DAO-controlled entity) and the node operator – must allocate four categories of risk and duty: (1) performance obligations (uptime, attestation accuracy, timely submission of proofs); (2) slashing liability (who absorbs the loss when the validator is penalized for downtime, double-signing or protocol violations); (3) cascade-risk allocation (what happens when a slashing event on the restaking layer triggers liquidation or forced exit from the base-layer staking position); and (4) upgrade and governance duties (who decides whether to adopt a network upgrade, exit a validator or migrate to a new restaking contract). Each of these is a legal question before it is a technical question. The smart contract enforces the outcome; the operator agreement defines who decided and who pays.

Operators we advise structure these relationships with explicit service-level expectations, capped liability where regulation permits and an escalation path for disputes – arbitration in a neutral forum rather than litigation in the staker's home jurisdiction. Where the operator is a separate legal entity from the protocol foundation, the agreement must also address intellectual-property licensing (the operator's right to use the protocol brand and code) and data-handling (validator logs and staker metadata cross borders and trigger GDPR or equivalent privacy obligations). The operator is not merely infrastructure for hire; in a restaking architecture the operator is a critical control point, and the legal documentation must reflect that role.

Slashing and cascade risk allocation

Slashing – the protocol-level penalty imposed on a validator for misbehavior or extended downtime – is the central risk in any proof-of-stake system. Restaking compounds that risk: a validator securing three networks through a restaking layer can be slashed on any of the three, and the penalty may propagate back to the base-layer staking position. If a validator's ETH is slashed because it attested incorrectly on a restaked oracle network, the liquid-staking derivative representing that ETH loses value, which may trigger liquidation in a lending protocol where the LSD was used as collateral. The cascade – slashing event → LSD price drop → collateral call → forced sale – can unwind positions across DeFi in minutes.

The legal question is who absorbs each layer of loss. The base-layer protocol (Ethereum, in the example above) enforces its slashing rules automatically; those penalties are not negotiable. But the allocation of loss between the restaking protocol, the node operator, the liquid-staking issuer and the end staker is a matter of contract and disclosure. A restaking protocol that socializes slashing losses across all stakers in a pool – the standard model – must disclose that mechanism clearly: a staker who believes her position is isolated from others' validator failures and then suffers a haircut from a distant slashing event has a claim for misrepresentation in many jurisdictions. A protocol that maintains a slashing-insurance fund financed by protocol fees or governance-token issuance shifts some risk to the protocol's balance sheet, which creates duties to stakers and may convert the insurance arrangement into a regulated insurance product if it is offered to the public.

Operators advising their legal teams on slashing allocation present us with three approaches: (1) operator-borne (the node operator's collateral or insurance absorbs the first loss, up to a cap); (2) protocol-borne (a DAO-controlled insurance pool covers slashing, funded by a share of staking rewards); (3) staker-borne (slashing losses are socialized pro rata among stakers, disclosed in the terms). Hybrid models are common. Each approach carries different disclosure, governance and regulatory implications. Operator-borne models may require the operator to hold capital or post collateral, which in some jurisdictions converts the operator into a regulated custodian or payment-service provider. Protocol-borne models create a contingent liability on the DAO's balance sheet and may trigger financial-reporting or securities-disclosure obligations. Staker-borne models place the heaviest burden on clear, prominent disclosure and a defensible click-through process – "I understand that slashing events affecting any validator in this pool will reduce my position" must appear before funds are committed, not buried in linked documentation.

Disclosure obligations for yield and validator performance

Yield is the marketing center of every restaking and liquid-staking product. A protocol advertises "12% APY" or "15% on restaked ETH," and that figure – however it is calculated – creates an expectation in the user's mind. If the actual yield delivered over the following months is materially lower, the user may have a claim for misrepresentation or, in jurisdictions that regulate investment advertising, a violation of financial-promotion rules. The legal obligation is not to guarantee yield – no competent counsel allows a guarantee – but to disclose the basis of the projection, the assumptions behind it and the risks that may cause actual performance to diverge.

In the United Kingdom, the Financial Conduct Authority's financial-promotion rules apply to any communication that invites a person to engage in investment activity; a crypto-asset that is a security or a specified investment falls squarely within scope. A restaking protocol marketing to UK users must ensure that yield claims are fair, clear and not misleading, that risk warnings are prominent and that the communication is approved by an FCA-authorized firm if the protocol itself is not authorized. Similar rules apply under MiCA for crypto-asset service providers marketing to EU retail clients: the whitepaper and all promotional material must contain standardized risk warnings, and any reference to past performance or projected returns must include the disclaimer that past performance is not indicative of future results. These are not box-ticking exercises; national regulators in member states are actively surveying DeFi frontends and issuing enforcement notices against issuers whose yield claims lack the required disclosures.

Validator performance – uptime, attestation success rate, historical slashing incidents – is the second disclosure burden. A protocol that selects or recommends specific validators must disclose the selection criteria and any conflicts of interest (for example, if the protocol foundation operates its own validator or receives a fee from recommended operators). Permissionless restaking, where any validator meeting objective on-chain criteria may join, reduces but does not eliminate this duty: the protocol must still disclose how the criteria are set, who can change them and what recourse a staker has if a validator underperforms. In our practice, disclosure for restaking and liquid-staking products includes a risk-factors section (slashing, cascade risk, smart-contract risk, liquidity risk, regulatory risk) presented before commitment, a validator-selection methodology available on request and a real-time or near-real-time dashboard showing validator performance and any slashing events in the pool. These are not optional; in a dispute, the existence and prominence of these disclosures is the first line of defense.

Entity structuring and progressive decentralization

A restaking or liquid-staking protocol does not exist in a legal vacuum. Somewhere, someone deployed the smart contracts; somewhere, a website hosts the frontend; somewhere, funds or fees accumulate. The question for the launch team is whether to operate through a traditional legal entity (a foundation, a limited company, a DAO-wrapper LLC) or to pursue full decentralization with no identifiable responsible party. Each path has regulatory and liability consequences. A protocol structured around a non-profit foundation in Switzerland or the Cayman Islands can contract with service providers, hold IP, employ counsel and negotiate with regulators – but the foundation is a legal person and can be sued, sanctioned or subject to disclosure orders. A fully decentralized protocol – governed by token vote, with no entity controlling the multisig, no official website and no identifiable development team – is harder to regulate but also harder to defend: when a regulator or a plaintiff cannot find a defendant, the pressure falls on the visible participants (the largest token holders, the frontend operators, the validators), and those parties face liability without the benefit of an entity's limited-liability shield.

Most serious protocols adopt a model of progressive decentralization: launch through a foundation or a DAO-adjacent entity that holds initial control, then transfer governance functions to token holders over a defined timeline as the protocol matures. The foundation's role narrows to maintaining non-discretionary infrastructure (the website, documentation, audits), while all material decisions – fee changes, validator inclusion criteria, treasury allocation – move on-chain to governance proposals. The legal advantage of this model is that it creates a clear record of the transfer of control, which supports the argument that the protocol is sufficiently decentralized that the token is not a security (or, under MiCA, that it does not confer rights typical of a transferable security). The timeline and the evidence matter: a protocol that announces decentralization but where the foundation retains an effective veto (through a controlling token stake, a multisig supermajority or off-chain influence over the core development team) has not achieved the legal substance of decentralization.

For restaking protocols specifically, the entity question extends to the relationship between the base protocol (the liquid-staking issuer) and the restaking layer. If both are controlled by the same foundation or the same set of insiders, regulators may collapse the structure and treat the entire stack as a single offering. If the restaking layer is genuinely independent – developed by a separate team, governed by a separate token, with no fee-sharing or IP-licensing arrangement that confers control – the two can be analyzed separately. Operators building in this space pressure-test independence early, because the structure is harder to unwind after launch than to design correctly from the start.

Cross-border regulatory interaction

Restaking and liquid-staking protocols are inherently cross-border. The stakers sit in fifty jurisdictions, the validators run in data centers across ten countries, the foundation is domiciled in one, the core team works remotely from three others, the DEX listing the LSD is accessed globally and the restaked collateral secures a network with its own set of node operators in yet more locations. Each of these touchpoints is a potential regulatory nexus. A protocol offering a security to US persons from a Cayman entity without SEC registration faces enforcement risk in the United States. A protocol whose validators are concentrated in the European Union may trigger MiCA compliance even if the issuer entity is offshore. A protocol that accepts fiat on-ramps or operates a custodial wallet in the flow may need money-transmitter or payment-institution licensing in the jurisdictions where users sit.

The cross-border analysis for a restaking protocol proceeds in three layers: (1) the token – is it a security, and where is it being offered? (2) the service – does operating the protocol, hosting the frontend or running the validator nodes constitute a regulated activity (dealing, arranging, custody, payment services)? (3) the entity – where does substance sit, and does that location impose licensing, tax or reporting obligations? The answers vary by jurisdiction. A non-custodial staking protocol that never touches user funds may not require a licence in Singapore (where the Payment Services Act regulates DPT services that involve customer funds) but may still require registration in the United Kingdom (where arranging or facilitating transactions in specified investments is a regulated activity). A liquid-staking issuer that qualifies as a CASP under MiCA in one EU member state can passport into others, but that passport is conditioned on the token not being a transferable security – if a national authority later concludes the LSD is a security, the MiCA authorisation is void and the issuer is in breach.

Operators we advise on cross-border restaking structures typically geo-fence jurisdictions where the regulatory risk exceeds the commercial opportunity (often the United States, pending clarity on digital-asset frameworks) and pursue licensing in one or two anchor hubs where they can establish substance. A foundation in the Cayman Islands or Switzerland combined with a MiCA CASP authorisation in an EU member state and a Payment Services Act licence in Singapore covers a large share of institutional and retail liquidity without overextending compliance resources. The key is that geo-fencing must be genuine – IP blocking, terms-of-service restrictions and KYC checks that enforce those restrictions – or it is treated as cosmetic by regulators.

Common mistakes in restaking and liquid-staking launches

The first common mistake is treating decentralization as a label rather than a state of fact. A protocol that launches with a blog post announcing "we are now decentralized" but where the foundation still controls the smart-contract upgrade keys, the treasury multisig and the website has not decentralized. Courts and regulators assess control by examining who can change the protocol, who receives the fees and who marketed the token at launch. If the answer to all three is the same party or group, the protocol is centralized for legal purposes, and the token is analyzed as a security issued by that party. True progressive decentralization requires a public timeline, a roadmap for transferring each function to on-chain governance and evidence that the transfers occurred (on-chain votes, multisig changes, dissolution of the foundation's discretionary authority). We see protocols stumble here by moving too slowly or by retaining emergency powers that undermine the decentralization narrative.

The second mistake is under-disclosing slashing risk. A user who stakes ETH directly on Ethereum understands, at least notionally, that downtime or misbehavior can reduce her balance. A user who buys a liquid-staking token marketed as "automatically compounding ETH staking rewards" may not understand that her token can lose value if any validator in the pool is slashed, or that restaking compounds that risk by exposing the position to slashing rules on multiple networks simultaneously. Disclosure must be explicit, placed before commitment and repeated in the interface where the user initiates the transaction. Generic risk warnings buried in terms of service do not satisfy this standard. In disputes we have reviewed, the plaintiffs' strongest claim is often misrepresentation: the protocol's marketing emphasized yield and liquidity but did not explain that both could evaporate in a cascade event.

The third mistake is ignoring the banking and on-ramp layer. A restaking protocol that never touches fiat still requires banking if the foundation pays service providers, if the core team draws salaries or if the protocol sells tokens in a fundraise. Many operators discover, after months building the protocol, that no bank will open an account for a Cayman foundation whose business is described as "operating a decentralized restaking network." The banking question must be addressed in parallel with the entity and token structure, not as an afterthought. Operators launching in this space typically need a banking relationship in a jurisdiction that permits digital-asset businesses (Switzerland, Singapore, Lithuania, the UAE) and an entity structure that satisfies the bank's risk and compliance desk. That often means a traditional foundation or company, not a DAO-adjacent entity with no board and no physical presence.

When to engage counsel

The right time to engage counsel for a restaking or liquid-staking protocol is before the token-economics model is finalized. Once the whitepaper is published and the marketing begins, the protocol's legal characterization is largely fixed: if the token was marketed on yield and the operator exercised discretion, changing the documentation later does not undo those facts. Counsel should be in the room when the team is deciding (1) whether the token is transferable, (2) whether rewards auto-compound or require a claim action, (3) who can change the validator set, (4) how slashing losses are allocated and (5) what the frontend says about expected returns. Each of those design choices has legal consequences, and the cost of restructuring after launch is an order of magnitude higher than the cost of designing correctly from the start.

Operators who wait until a regulatory inquiry or a user dispute to instruct counsel face two problems: the legal advice is reactive (defending a position rather than structuring to avoid it), and the factual record is already written. A securities regulator assessing whether a token is an investment contract will look at the launch materials, the initial token distribution, the public statements by the founders and the degree of centralization at the time of the offering. If those facts point toward a securities offering, a later pivot to decentralized governance or a retrospective legal opinion does not change the analysis. Engaging counsel early allows the protocol to build the evidentiary record – governance votes, technical audits, progressive-decentralization milestones – that supports the legal position the team wants to take.

For operators building restaking or liquid-staking protocols, the scoping call with OBOLUS typically covers the token-classification analysis, the entity and jurisdiction choice, the operator-agreement framework and the disclosure model. The fixed-scope engagement runs from initial assessment through to a legal opinion on the token's classification, a set of operator agreements and disclosure documents, and a memo on the cross-border licensing picture. Where a protocol is preparing for a fundraise or an exchange listing, we layer in the legal-opinion work that investors and listing venues require. The work is modular: operators decide which pieces they need now and which can follow in a later phase, but the token-classification analysis is never optional.

For an initial assessment of your restaking or liquid-staking structure – token classification, operator duties and cross-border licensing – contact OBOLUS at info@oboluslaw.com. We scope the work as a fixed-price mandate with defined deliverables, and the first strategy call is under NDA at no charge.

Decision matrix: operator profile to structure

Protocol teams building restaking or liquid-staking products fall into three broad profiles, each with a different legal and entity path. Profile A: institutional-backed protocol – a team with venture funding, planning a token-generation event and seeking exchange listings for the LSD. This profile typically requires a Cayman or Swiss foundation (for the fundraise and the token issuance), a MiCA CASP authorisation in an EU member state (for retail access in Europe), banking in Switzerland or Singapore and formal operator agreements with professional node operators. The token-classification question is central: if the LSD is a security, the path is registration or an exemption (Regulation S, Regulation D in the United States; prospectus exemptions in the EU). If it is a utility token or sufficiently decentralized, the path is CASP authorisation under MiCA and the Payment Services Act in Singapore. Timeline from instruction to launch: nine to fifteen months, assuming no re-work on the tokenomics.

Profile B: DAO-native protocol – a community-governed project with no formal fundraise, deploying contracts under a DAO-wrapper LLC or a minimalist foundation. The DAO holds the multisig, votes on all material changes and distributes governance tokens to contributors and users. This profile prioritizes decentralization over institutional access: no exchange listings, no venture investors, no fiat on-ramps. The legal work centers on the DAO wrapper (a Marshall Islands or Wyoming DAO LLC is common), the operator agreements (often with individual validators rather than corporate operators) and the disclosure framework (published documentation, risk warnings on the frontend, but no formal prospectus). Regulatory risk is managed by geo-fencing high-risk jurisdictions and avoiding any conduct that looks like a public offering of securities. Timeline: four to six months, lighter touch, with ongoing governance support as the DAO matures.

Profile C: infrastructure operator – a corporate entity running validator nodes for hire, offering restaking as a service to protocols and institutional stakers. This profile is not issuing a token; it is providing infrastructure. The legal questions are the operator agreements (service levels, liability caps, slashing allocation), the classification of the service (is it custody, payment processing, or neither?) and the licensing requirements in the jurisdictions where the validators run. An operator whose validators secure networks for clients in the EU may need authorisation as a crypto-asset service provider under MiCA if the service involves holding or controlling customer assets. An operator in Singapore may need a Payment Services Act licence depending on the flow of funds. The entity is typically a traditional limited company in a jurisdiction with clear licensing paths and stable banking. Timeline: three to six months for the operator agreements and the licensing roadmap.

Related at OBOLUS

FAQ

Can a decentralised protocol be regulated?

Yes, if the protocol or its operators perform regulated activities or if the token is a security. Decentralization is not a regulatory exemption; it is a factual question about control. A protocol with no identifiable operator, no controlling foundation and genuinely permissionless governance may fall outside traditional licensing regimes, but the participants – validators, frontend hosts, token holders with sufficient influence – can still face liability or enforcement. Regulators assess who exercises discretion, who receives fees and who marketed the offering. Where those functions sit with identifiable parties, regulation applies.

Who is liable when a smart contract fails?

Liability for a smart-contract failure – a bug, an exploit, an unintended cascade event – depends on the facts: who deployed the contract, who audited it, what representations were made to users and whether the terms of service contain effective liability exclusions. A fully decentralized protocol with no controlling entity and clear disclaimers may limit the developer's liability, but plaintiffs often target the foundation, the token issuers or the validators on theories of negligence, breach of fiduciary duty or misrepresentation. In England and other common-law jurisdictions, a party that exercises discretion over another's assets on trust-like terms can incur equitable duties that cannot be excluded by contract. The safest path is professional audits before deployment, clear risk disclosure and liability caps that comply with applicable consumer-protection law.

What wrapper suits this structure?

The choice of legal wrapper – foundation, DAO LLC, limited company – depends on the protocol's profile and the target market. A venture-backed protocol preparing for a token sale and exchange listings typically uses a non-profit foundation in the Cayman Islands or Switzerland, which can issue tokens, contract with service providers and hold IP. A community-governed DAO-native protocol uses a DAO wrapper LLC (Marshall Islands or Wyoming) or a minimal foundation with on-chain governance controlling all material decisions. An infrastructure operator running validators for hire uses a traditional limited company in a jurisdiction with licensing frameworks and stable banking. The wrapper must support the protocol's substance (where the team works, where the servers run, where banking lives) and the regulatory strategy (MiCA authorisation, SEC registration or exemption, geo-fencing). No single wrapper fits every protocol; the analysis starts with the business model and the user base.

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 restaking and liquid-staking work covers token classification against the substance-of-rights test, operator-agreement drafting for slashing and cascade-risk allocation, progressive-decentralization roadmaps and cross-border licensing strategies. We structure licensing, banking and tax as one mandate rather than three disconnected workstreams, and we assess classification against the substance of rights, not the marketing label. To discuss your situation, contact info@oboluslaw.com or visit our contact page.

By Roman Levitt, Technology & DeFi Counsel – specialising in the legal structuring of DeFi protocols, smart-contract risk allocation and the classification of novel token instruments under securities and commodities frameworks.

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