EST · MMXXVI
Home/Insights/Technology & DeFi/Restaking Protocols: Securities Analysis of Reward Instruments
DeFi, Tokenization & Smart-Contract Law

Restaking Protocols: Securities Analysis of Reward Instruments

Restaking Protocols: Securities Analysis of Reward Instruments. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee en

A protocol that lets users stake PoS assets to one validator, then restake the same principal to a second validation layer, creates two reward flows and at least one tradable receipt token. When that receipt token accrues value from protocol fees or from secondary staking yield, the question moves from "is this a utility?" to "is this an investment contract?" The legal classification turns on the economic substance of the arrangement, the degree of managerial effort by a promoter, and the reasonable expectation of profit from that effort – not on the label "liquid staking token" or "restaking points" in the documentation.

Restaking protocols represent a recent DeFi primitive: instead of locking capital in a single proof-of-stake validator, the holder delegates the same base asset to multiple validation or security layers simultaneously, extracting compounded rewards. The architecture introduces intermediate receipt tokens (often liquid, tradable representations of the staked position), a protocol-operated reward-distribution mechanism, and frequently a governance or fee-capture layer that channels value back to token holders. Each of these components carries classification risk under securities frameworks across the major digital-asset regimes.

This analysis maps how restaking reward instruments and their associated receipt tokens are assessed against the investment-contract tests in the United States, the transferable-securities definition under MiCA, and the capital-markets perimeters in Singapore, Hong Kong, Abu Dhabi and Switzerland. It addresses the structural choices that protocols make to document a defensible classification, the points at which decentralization materially changes the analysis, and the cross-border reality that a single instrument can fall on opposite sides of the line in different regimes. For teams building restaking infrastructure, the window to settle classification questions sits before the first external capital commits – not after the first enforcement letter arrives.

Is a restaking receipt token an investment contract under US law?

Under the *Howey* test, an investment contract exists when there is an investment of money in a common enterprise with a reasonable expectation of profit derived from the efforts of others. A restaking protocol that issues a liquid receipt token (e.g., a token representing a claim on staked ETH plus accrued rewards from multiple validators) meets the first two prongs immediately: users contribute assets, and those assets are pooled or managed collectively by the protocol's smart contracts and the validator set it coordinates. The analysis pivots on the third and fourth prongs – expectation of profit and the source of that profit.

If the protocol advertises expected APY, distributes fee revenue from validator operations to token holders, or implements an automated compounding mechanism that reinvests rewards on behalf of users, the expectation-of-profit element is satisfied. The "efforts of others" inquiry examines who selects validators, who monitors slashing risk, who upgrades the protocol's contracts, and who markets the system to attract deposits. Where a core team or foundation performs these functions – particularly in the first 12 to 24 months after launch – the arrangement carries significant investment-contract risk. The SEC's position, reflected in enforcement actions against staking-as-a-service platforms, is that even automated smart-contract operations constitute "efforts of others" when a promoter designed, deployed and continues to control or influence the system.

Receipt tokens that are liquid and tradable on secondary markets add a second classification risk: the token itself may be a security independent of the underlying staking arrangement. If the token's value derives primarily from the protocol's ongoing management of the staked pool and from the market's expectation that the protocol will generate returns, the token exhibits the characteristics of an equity interest or profit-participation right. The distinction between a pure claim token (a wrapped representation with no additional rights) and a profit-bearing receipt token is critical. A claim token that merely tracks the principal and can be redeemed 1:1 is closer to a digital certificate of deposit; a receipt token that accrues fees, governance weight or secondary staking yield is closer to a security.

In our cross-border DeFi practice, we have seen protocols attempt to exit investment-contract risk by eliminating the receipt token's tradability (a lockup structure) or by fully decentralizing validator selection through an on-chain governance vote before any external deposit. Neither approach is a safe harbor. A lockup removes liquidity but does not remove the expectation of profit derived from the validator's efforts. A governance vote conducted when token distribution is still concentrated in the hands of the founding team does not constitute meaningful decentralization. The SEC's framework, though not binding law, treats a protocol as sufficiently decentralized only when no single group can unilaterally alter the system, when the code is immutable or governed by a genuinely dispersed token-holder base, and when information asymmetries between insiders and users are minimal. Few restaking protocols meet that standard at launch.

For protocols building a restaking layer in a market where US users may participate, the question is not whether to classify but when and how to register or qualify for an exemption. The typical paths are Regulation D (private placement, accredited investors only), Regulation A (a mini-public offering with disclosure requirements and a funding cap), or Regulation S (an offshore offering with no US promotion). Each carries trade-offs in cost, timeline and operational restrictions. The alternative – launching without a US exemption and arguing post-facto that no security exists – exposes the protocol, its contributors and often its venture backers to strict-liability violations under Section 5 of the Securities Act. To map your protocol's exposure before the next funding round, contact OBOLUS at info@oboluslaw.com.

How does MiCA treat restaking rewards and receipt tokens?

The Markets in Crypto-Assets Regulation distinguishes crypto-assets that are financial instruments (governed by MiFID II) from those that are "other" crypto-assets (governed by MiCA's Title III or IV). A crypto-asset is a financial instrument, and thus outside MiCA's scope, if it qualifies as a transferable security under MiFID II – essentially, an instrument that is negotiable on the capital market and that confers rights akin to shares, bonds or other securities. The test is functional: does the instrument represent ownership, a creditor claim or a profit-participation right in a legal entity or an unincorporated venture?

A restaking receipt token that confers only a claim to withdraw the original staked asset typically falls within MiCA as an "other" crypto-asset, not a transferable security. The token represents a digital IOU, not an equity stake. However, if the receipt token carries additional rights – a share of protocol fee revenue, voting weight over validator selection, or a priority claim in a liquidation – the instrument begins to exhibit the characteristics of a share or a profit-participation certificate. European regulators, guided by ESMA's opinions, apply a substance-over-form analysis: the label "utility token" or "staking derivative" is irrelevant if the economic reality is that holders are investing in a venture with the expectation that the protocol's managerial decisions will generate returns.

The second classification question under MiCA is whether the token is an asset-referenced token (ART) or an e-money token (EMT). An ART is a token that purports to maintain a stable value by referencing another asset or a basket of assets. A restaking receipt token that is soft-pegged to the value of the underlying staked asset (e.g., 1 rETH ≈ 1 ETH) may be assessed as an ART if the protocol actively manages the peg through arbitrage mechanisms or reserve adjustments. The ART classification triggers issuer authorisation under Title IV, a capital requirement, and reserve composition rules. Most restaking protocols avoid ART treatment by allowing the receipt token to float freely (its market price reflects the staked principal plus accrued rewards, without a stabilisation mechanism), but that design choice can increase price volatility and liquidity risk for users.

Where a restaking protocol is structured as a decentralised autonomous organisation with no legal entity, the transferable-securities analysis under MiFID II becomes difficult to apply: there is no issuer in the traditional sense. ESMA has indicated that the absence of a legal issuer does not automatically exclude an instrument from the securities perimeter if the economic substance is that of an investment contract. In practice, European national competent authorities have been reluctant to classify purely decentralised arrangements as securities, preferring to wait for MiCA's "other crypto-asset" rules to take effect. That regulatory forbearance may not last. Protocols that begin life as fully decentralised experiments and later introduce a foundation, a treasury or a core development team funded by protocol fees cross back into the securities perimeter.

MiCA's other-crypto-asset regime, governed by Title III, imposes whitepaper disclosure obligations on issuers. A restaking protocol that issues a tradable receipt token to EU users must publish a crypto-asset whitepaper disclosing the project, the rights conferred by the token, the principal risks, and the technology and governance model. The whitepaper must be notified to the competent authority of the issuer's home member state before the token is offered. If the protocol has no legal entity and no EU establishment, the notification obligation is difficult to satisfy, and EU market access becomes legally uncertain. For protocols that plan to serve EU users at scale, the practical path is to establish an entity in a member state, notify the whitepaper, and eventually obtain a CASP authorisation (the MiCA licence for crypto-asset service providers) or partner with a licensed EU exchange.

What is the capital-markets-products test in Singapore, and when does a restaking token trigger it?

Singapore's Monetary Authority assesses digital tokens under the Securities and Futures Act, which defines a capital-markets product to include securities (shares, debentures, units in a collective investment scheme) and derivatives. A token is a security if it confers rights that are characteristic of equity or debt: a share in profits, a right to vote on the issuer's affairs, or a creditor claim with a fixed return. A token is a unit in a collective investment scheme (CIS) if investors' contributions are pooled, the scheme is managed as a whole by an operator, and participants have no day-to-day control over the management of the property.

A restaking receipt token issued by a protocol that pools users' assets, selects validators on their behalf, and distributes rewards automatically through a smart contract typically satisfies the CIS test. The pooling element is clear: all deposited assets sit in a common staking pool managed by the protocol's contracts. The management element is satisfied where a core team or an algorithm designed by that team makes the economically significant decisions – which validators to delegate to, how to allocate stake, how to handle slashing events. The fact that management is automated through code does not remove it from the CIS definition; the relevant question is whether the code was designed and deployed by a promoter who continues to benefit from the arrangement.

MAS has issued guidance (the Payment Services Act guidelines and various consultation papers on digital tokens) indicating that a token will escape CIS classification if it is genuinely decentralised from inception – meaning no person or group has control over the protocol, the code is open-source and immutable, and decision-making is distributed among a wide, unrelated set of participants. Few restaking protocols meet that standard in their first year. Most are launched by a core team, funded by venture capital, and governed (if at all) by a token distribution that is heavily weighted toward insiders. In that posture, the protocol and its receipt token are likely a CIS, and offering the token to Singapore users without a capital-markets services licence is an offence under the SFA.

The licensing requirement for a CIS operator is onerous: the operator must be a corporation, must hold a capital-markets services licence for fund management, must meet minimum capital requirements that scale with assets under management, and must comply with MAS's ongoing conduct and disclosure standards. For a DeFi protocol that values pseudonymity and decentralisation, incorporating a Singapore entity and applying for a CMS licence is often a non-starter. The alternative paths are to exclude Singapore users through geofencing (verifiable via IP and KYC controls), to restructure the protocol so that it qualifies as a payment token (a pure medium-of-exchange with no investment features) under the Payment Services Act, or to delay the Singapore launch until the protocol is sufficiently decentralised that the CIS analysis no longer applies.

A second risk in Singapore is the derivatives classification. If the restaking receipt token derives its value primarily from an underlying reference asset (the staked ETH or SOL), and if the token's terms allow cash settlement or leverage, the token may be a derivative contract. Derivatives fall under the SFA's capital-markets-products regime and trigger even stricter licensing requirements. Most restaking protocols avoid this classification by ensuring that the receipt token is redeemable only for the underlying staked asset, not for cash, and by eliminating any leverage or margining mechanism. However, if a secondary market develops where the receipt token trades at a significant premium or discount to the underlying, and if arbitrageurs use the token in leveraged strategies, the line between a claim token and a derivative can blur.

Is a restaking token a virtual asset or a security under Hong Kong's VASP regime?

Hong Kong's Securities and Futures Commission licenses virtual-asset trading platforms (VATPs) under a regime that treats virtual assets and securities as separate but overlapping categories. A virtual asset, as defined in the Anti-Money Laundering Ordinance, is a digital representation of value that can be traded or transferred electronically and is used for payment or investment purposes, but does not include fiat currency, securities, futures contracts or other instruments already regulated under the SFO. The critical question for a restaking receipt token is whether it crosses into the securities or CIS perimeter, or whether it remains a "pure" virtual asset.

A token is a security in Hong Kong if it represents shares in or debentures of a corporation, or if it confers a right to participate in profits or assets of a collective investment scheme. The CIS test in Hong Kong is similar to Singapore's: pooling, management by an operator, and the participant's lack of day-to-day control. A restaking protocol that issues a receipt token to Hong Kong users, pools their assets, and manages the staking operations centrally (even if "centrally" means through automated smart contracts controlled by a core team) likely operates a CIS. Offering interests in a CIS to the Hong Kong public without SFC authorisation is a criminal offence.

If the token does not qualify as a security or CIS interest, it is a virtual asset, and a platform that trades it must hold a VATP licence. The VATP licence requires the operator to be incorporated in Hong Kong, to meet capital adequacy and insurance standards, to implement robust custody and AML controls, and to restrict services to professional investors (in the early phase) or to retail investors who pass a knowledge test (under the expanded regime). The regime is designed for centralised exchanges; applying it to a decentralised protocol is conceptually challenging. The SFC's position, articulated in circulars and licensing decisions, is that if a protocol has an identifiable operator – a legal entity, a foundation, or even a loose group of developers who benefit from the protocol – that operator should seek a licence or exclude Hong Kong users.

Hong Kong courts have begun to recognise crypto-assets as property capable of being the subject of proprietary relief. In the first tokenised injunction (HCA 2417/2024), the court granted a proprietary injunction to prevent the dissipation of NFTs stored in a wallet. In *Re Gatecoin* (2023 HKCFI 914), the court held that cryptocurrencies are "property" for insolvency purposes. These decisions confirm that restaking receipt tokens, even if not classified as securities, carry legal rights enforceable in Hong Kong courts. That enforceability cuts both ways: token holders can bring claims against a protocol for mismanagement or breach of the token's terms, and a protocol that fails to honor redemption requests or that suffers a slashing event may face litigation in Hong Kong even if the protocol has no formal presence there. For protocols considering Hong Kong users, the question is not only "do we need a licence?" but also "what law governs the token, and where will disputes be litigated?"

How does ADGM's FSRA assess restaking instruments under its recognised-virtual-assets framework?

The Financial Services Regulatory Authority within the Abu Dhabi Global Market regulates virtual-asset activities under a framework that distinguishes recognised virtual assets (which may be offered and traded within ADGM) from those that are securities or other specified investments under the Financial Services and Markets Regulations. A virtual asset is recognised if it is approved by FSRA or if it falls within a category designated by FSRA guidance. A restaking receipt token that represents a claim on staked crypto-assets and that does not confer equity-like rights or a profit share linked to the issuer's enterprise may qualify as a recognised virtual asset, subject to FSRA's case-by-case assessment.

If the token confers rights beyond a simple claim – for example, a share of protocol fee revenue, governance rights that materially affect the protocol's economic direction, or a liquidation preference – it is likely a specified investment (the ADGM equivalent of a security) and subject to the full capital-markets regulatory perimeter. That perimeter includes a requirement for the issuer to be authorised by FSRA, to publish a prospectus or offering document, and to comply with ongoing disclosure and corporate-governance obligations. The distinction between a recognised virtual asset and a specified investment is not always clear in the case of DeFi protocols, because the "issuer" may be a smart contract with no legal personality, and the "governance" may be exercised by a dispersed and pseudonymous set of token holders.

FSRA has taken a pragmatic approach: where a protocol is genuinely decentralised (no central operator, immutable code, governance by a wide distribution of tokens) and where the token does not promise or pay returns linked to a promoter's efforts, FSRA is more likely to treat the token as a virtual asset rather than a security. However, that leniency does not extend to protocols that launch with a core team, a private token sale, and a roadmap that includes revenue-sharing or staking-rewards enhancements. In those cases, FSRA expects the promoters to establish an ADGM entity, apply for a financial-services permission, and structure the token offering in compliance with ADGM's prospectus and marketing rules.

One common structuring path for restaking protocols serving ADGM users is to partner with an ADGM-licensed virtual-asset service provider. The licensed entity acts as the interface between the protocol and ADGM users: it holds the FSRA permission, it conducts KYC/AML checks, it holds users' assets in custody or escrow, and it interacts with the protocol's smart contracts on the users' behalf. The protocol itself remains offshore and does not directly offer its tokens into ADGM. This model transfers some regulatory risk to the licensed intermediary and allows the protocol to avoid the full weight of ADGM financial-services regulation, but it also introduces counterparty risk, custody risk, and potential liability if the intermediary's controls fail. For protocols that expect a meaningful ADGM user base, the trade-off is often acceptable; for those targeting global retail, the cost and complexity of an ADGM partnership may not justify the access.

What is FINMA's token taxonomy, and where do restaking rewards sit within it?

Switzerland's Financial Market Supervisory Authority distinguishes three token types: payment tokens (pure medium of exchange, functionally equivalent to cryptocurrency), utility tokens (granting access to a digital service or application), and asset tokens (representing a claim on an asset or a participation in future earnings). The classification is not exclusive – a token can have features of more than one type, in which case FINMA applies the requirements of all applicable categories. A restaking receipt token that allows holders to redeem staked assets and that also accrues protocol fees or staking yield is likely a hybrid: partly a claim token (asset category) and partly a profit-participation instrument (security).

Asset tokens that function as securities (by representing equity, debt or a profit-sharing right) trigger Switzerland's securities-law perimeter: the prospectus requirement under the Financial Services Act, the licensing requirement for securities dealers, and the conduct rules for asset managers if the token involves discretionary management of investors' funds. A restaking protocol that pools ETH from multiple users, delegates it to validators chosen by a protocol team, and distributes the resulting rewards is exercising discretionary management. If the protocol is organised as a legal entity or if a foundation controls the protocol's treasury or upgrades, that entity is likely an asset manager under Swiss law and must apply for a FINMA licence unless it falls within a small-asset exemption (currently set at an assets-under-management threshold, the exact figure of which varies by the type of management and should be verified from the current FSA and FINMA ordinances).

Utility tokens are the least regulated category: if a token's sole function is to grant access to a protocol's services, and if the protocol is live and functional at the time of the token sale, FINMA does not treat the token as a security. The difficulty for restaking protocols is that few can credibly claim a pure-utility function. A liquid staking or restaking token that is tradable, that appreciates in value as staking rewards accrue, and that is marketed on the basis of expected APY is not granting access to a service in the way a decentralised-storage access token does. It is a financial instrument that allows users to earn a return from locking capital in a managed pool.

FINMA's published ICO guidance sets out a safe-harbor test: if the token is issued in connection with a functional blockchain and the token's primary purpose is consumption (not investment), the token is a utility token. Restaking receipt tokens rarely satisfy that test. The blockchain may be functional, but the token's purpose is to represent a financial claim and to earn yield, not to consume a service. The investment motive is plain in the protocol's marketing materials, in the APY estimates published on aggregator sites, and in the fact that secondary markets trade the token at a premium when yield expectations rise. FINMA's classification follows economic substance, not the language in the whitepaper. Calling a token "utility" or "access" does not insulate it from securities treatment if the reality is that buyers are investing capital with the expectation that the protocol's management will generate returns.

Does true decentralisation remove a restaking protocol from the securities perimeter?

Decentralisation is a spectrum, not a binary state. At one end: a protocol deployed by a named team, controlled by a multi-sig wallet held by that team, marketed through a venture-backed foundation, with a token distribution concentrated among insiders. At the other end: a protocol launched anonymously, governed entirely by on-chain voting weighted by a widely distributed governance token, with immutable core contracts and no mechanism for a single party to withdraw funds or alter the reward logic. The first is almost certainly within the securities perimeter across every major regime. The second may not be, but only if decentralisation is achieved at or before the point of first external investment.

In the United States, the SEC's framework for analysing decentralised networks (articulated in Director Hinman's 2018 speech on Ethereum and later incorporated into enforcement settlements) treats a network as sufficiently decentralised when: (1) the network is operational and functional for its intended purpose, (2) token holders have governance rights and genuinely exercise them, (3) the protocol's code is open-source and not subject to unilateral amendment by any person or group, (4) information about the network is widely available and not asymmetrically held by insiders, and (5) no active promoter is making efforts on which purchasers would reasonably rely to generate returns. If all five conditions are met, the token is more like a commodity or a pure digital asset than an investment contract, and the SEC is unlikely to assert jurisdiction.

The problem for most restaking protocols is that they launch before achieving that level of decentralisation. The protocol is deployed by a core team that retains the ability to upgrade contracts, to add or remove validators, or to adjust fee parameters. A governance token exists, but its distribution is skewed toward venture investors and the founding team, so votes are not genuinely decentralised. The protocol is marketed on the basis of a roadmap that includes new features, integrations and yield-enhancement strategies – all of which signal that ongoing managerial effort by the promoters is expected to drive returns. In that posture, the protocol is an investment contract, and the receipt token is a security.

Some protocols attempt to accelerate decentralisation through an "immutable deployment" strategy: the core contracts are deployed with no upgrade key, governance is launched simultaneously with the protocol, and the founding team publicly burns any special privileges. That approach can shorten the window during which the protocol is within the securities perimeter, but it does not eliminate the risk entirely. If the protocol was marketed to early investors during a period when the team controlled it, those early sales are securities offerings even if the protocol later decentralises. The SEC has made clear that decentralisation is not retroactive: it does not cure an unregistered securities offering that occurred before the network was decentralised. Protocols that raised venture funding through a SAFT (Simple Agreement for Future Tokens) or a similar instrument must assume that those sales are securities offerings and structure them under Regulation D or another exemption.

Under MiCA and in most European regimes, decentralisation does not provide a categorical exemption from securities or crypto-asset regulation. A fully decentralised protocol may fall outside the transferable-securities definition if there is no identifiable issuer, but it still issues a crypto-asset that must comply with MiCA's whitepaper and transparency obligations if offered to EU users. The practical result is that even a decentralised restaking protocol must find a way to publish a compliant whitepaper and notify it to a competent authority, or must geofence EU users entirely. The former is difficult without a legal entity; the latter is increasingly hard to enforce as VPN use and decentralised front-ends proliferate. The tension between decentralisation as a technical ideal and regulation as a legal requirement remains unresolved in most jurisdictions.

What does defensible classification documentation look like for a restaking protocol?

A defensible classification begins with a written legal analysis prepared before the protocol launches or before the first token sale to non-founders. The analysis maps the protocol's design against the securities tests in every jurisdiction where users may reasonably participate, identifies the classification under each regime, and documents the facts and features that support the protocol's chosen characterisation. The analysis is not a marketing document; it is an internal memo that can be shared with investors, exchanges and regulators if the protocol's classification is later challenged. The analysis should be updated every time the protocol's features change materially – when governance is introduced, when a fee-sharing mechanism is added, when a new validator set is integrated.

The core of the analysis is a substance-over-form assessment of the token's rights and the protocol's operations. What exactly does the receipt token represent? A claim on specific staked assets, redeemable 1:1? Or a share of a pooled staking position, where redemption depends on the protocol's liquidity or on the protocol unwinding positions in the market? Who selects the validators, and how? Is validator selection automated by the protocol's contracts, or does a team manually curate a validator set? How are rewards distributed – directly to token holders' wallets, or accumulated in the protocol and claimed on demand? Is there a fee charged by the protocol, and if so, who receives it?

Each of these design details affects the classification. A token that is redeemable 1:1 for the underlying asset, with no protocol fee and no profit-sharing, is closer to a wrapped asset than a security. A token that accrues value from protocol fees, that is governed by a centralized team, and that depends on the team's ongoing selection of high-yield validators is an investment contract. The classification memo must describe the protocol's actual operations, not the theoretical model in the whitepaper. If the protocol's documentation says governance is decentralised but 80 per cent of governance tokens are held by the founding team and their investors, the memo must state that fact.

Defensible documentation also includes a disclosure document – either a prospectus (if the protocol is conducting a registered offering), an exemption notice (if relying on a private-placement or offshore exemption), or at minimum a whitepaper that complies with MiCA's standards or with the local equivalent. The disclosure must cover the protocol's purpose, the rights conferred by the token, the risks (including smart-contract risk, slashing risk, regulatory risk, liquidity risk), the protocol's governance model, the identity or pseudonymity of the team, the token distribution and vesting schedule, and the use of proceeds if the protocol is raising capital. The disclosure is evidence that the protocol treated the token offering as a financial transaction, not as an unregulated software release.

A third element is proof of decentralisation, where applicable. If the protocol's defense against securities classification is that it is sufficiently decentralised, the protocol must be able to demonstrate that decentralisation was achieved before the first external offering. The evidence includes: timestamped contract deployments showing no admin key, governance proposals and vote records showing community participation, token-distribution data showing wide dispersion, and attestations or technical audits confirming that no person or group can unilaterally alter the protocol. Many protocols publish a "progressive decentralisation roadmap" setting target dates for removing each centralized control. That roadmap is evidence of good intent, but it is not a defense against a securities claim for token sales that occur before the roadmap is complete. The timing of decentralisation is everything.

What entity and jurisdiction structure minimises exposure for a restaking protocol?

The structural choice most restaking protocols face is whether to operate through a legal entity (a foundation, a DAO LLC, or a corporation) or to launch as a pure smart-contract protocol with no legal wrapper. Operating through an entity provides limited liability, a counterparty that can enter contracts, a vehicle that can hold a bank account or a treasury, and a legal home that clarifies jurisdiction and governing law. It also creates a clear target for regulators: if the entity controls the protocol, the entity is the issuer, and the entity's home jurisdiction determines which securities and financial-services laws apply.

The most common entity structures for DeFi protocols are a Cayman Islands foundation company, a Swiss foundation (Stiftung), a Marshall Islands DAO LLC, or a Wyoming DAO LLC. Each offers limited liability and a legal personality separate from the protocol's contributors. The Cayman foundation is the most widely adopted: it is purpose-built for non-profit or community-driven projects, it offers tax neutrality, it has an established legal and service-provider ecosystem, and Cayman law does not impose onerous governance or disclosure requirements on foundations. A Cayman foundation can hold the protocol's IP, employ the core development team, receive grants or donations, and govern the protocol's treasury, all while maintaining a clear separation between the foundation's activities and the automated operations of the protocol's smart contracts.

A Swiss foundation offers similar benefits with the added credibility of Switzerland's mature legal system and FINMA's relatively clear token guidance. The downside is cost and complexity: Swiss foundations are more expensive to establish and maintain, Swiss law imposes fiduciary duties on the foundation council, and FINMA will assert jurisdiction over the foundation's activities if those activities include managing pooled assets or issuing securities. For protocols that plan to serve Swiss users or that want the reputational signal of a Swiss domicile, the trade-off may be worthwhile. For protocols that prioritise flexibility and lower overhead, Cayman is typically the better choice.

The DAO LLC (whether Marshall Islands or Wyoming) is a newer option designed specifically for decentralised autonomous organisations. The structure wraps a DAO in a legal entity, with the DAO's token holders as members and the DAO's smart contracts as the governance mechanism. The appeal is that the structure recognises decentralised governance as a legitimate form of management, and it offers limited liability to token holders (protecting them from personal liability for the DAO's actions). The disadvantages are lack of legal precedent – no court has yet ruled on how a DAO LLC's governance provisions are enforced when members are pseudonymous and dispersed globally – and regulatory uncertainty about whether a DAO LLC is a valid issuer under securities laws. For restaking protocols that are genuinely decentralised from day one, a DAO LLC is conceptually attractive; for those with a core team and concentrated control, a traditional foundation or company is a safer choice.

Where the protocol has no legal entity, every contributor is potentially personally liable for the protocol's obligations and regulatory violations. If a bug in a restaking contract causes user losses, affected users may bring tort or contract claims against the developers, the auditors, the front-end operators, or anyone else who touched the protocol. If a regulator determines that the protocol is an unregistered securities offering or an unlicensed collective investment scheme, enforcement action can be brought against the individuals who promoted, developed or benefited from the protocol. The anonymity that many DeFi protocols prize is not a legal shield: blockchain forensics, front-end domain registration, GitHub commit histories, social-media accounts and transaction flows from the protocol to known wallets can all be used to identify responsible parties. For protocols handling more than a few million dollars in user assets, operating without a legal entity is a significant personal-liability risk for every participant.

How do you structure for regulatory optionality without pre-committing to a licence?

Regulatory optionality means keeping multiple licensing paths open while the protocol scales and while the regulatory landscape settles. The goal is to build the protocol in a way that allows it to apply for a licence if and when that becomes necessary or advantageous, without structuring around one regime's requirements so tightly that the protocol becomes uncompetitive or incompatible with other regimes. The technique is to separate the core protocol (the immutable or minimally governed smart contracts) from the periphery (the front-ends, custody arrangements, fiat on-ramps, marketing, and customer-facing operations).

The core protocol should be as neutral as possible: it accepts deposits from any address, it executes staking and reward distribution automatically according to its code, and it does not perform KYC, IP geofencing, or jurisdiction-specific compliance. That neutrality preserves the protocol's censorship resistance and allows it to remain outside the direct regulatory perimeter in jurisdictions where truly decentralised protocols are not subject to licensing. The periphery – the website or dApp interface that users access to interact with the protocol – is where compliance controls sit. The interface can implement KYC, can restrict access by jurisdiction, can display disclosures required by local law, and can route user funds through a licensed custodian or payment provider where necessary.

This two-layer approach allows the protocol's operators to obtain a licence in one or more flagship jurisdictions (for example, a MiCA CASP authorisation in the EU, a VASP licence in ADGM, or a Payment Institution licence in Singapore) and to offer the licensed service only to users in those jurisdictions, while the core protocol remains accessible to users globally through alternative front-ends or direct smart-contract interaction. The licensed entity becomes the "regulated face" of the protocol for institutional users, banks and users in restrictive jurisdictions; the protocol itself remains open and permissionless for users elsewhere. This is the model adopted by many leading DeFi lending and exchange protocols, and it allows the protocol to compete in both compliant and non-compliant markets without sacrificing the underlying decentralised architecture.

A second dimension of optionality is token-sale structure. Rather than conducting a single public sale that must comply with the strictest regime in your user base, structure the initial distribution as a series of private placements under Regulation D (US), Regulation S (offshore), or equivalent exemptions in other jurisdictions, with each placement tailored to the accredited-investor or qualified-purchaser standard in that jurisdiction. Public access to the token comes later, through secondary-market listings on licensed exchanges or through a fair launch where tokens are distributed to protocol users based on their participation. The fair-launch model – where no tokens are sold for cash, but instead are earned through providing liquidity, validating, or contributing to governance – is the least likely to trigger securities regulation, because there is no investment of money and no promoter selling a financial interest.

The trade-off with fair launches is that they make it harder to raise development capital. Venture investors want a SAFT or a token purchase agreement that gives them a defined allocation at a discount to the eventual market price. If the protocol cannot offer that, the investor has no way to participate early. One compromise is a hybrid launch: a small private sale to strategic investors under a securities exemption, combined with a broad fair launch where the majority of tokens are distributed for free based on protocol usage. The private investors receive their tokens subject to a vesting schedule, the community receives tokens through participation, and the protocol's classification risk is reduced because the primary distribution is not a sale. The private sale is clearly a securities offering, but it is structured under an exemption, documented, and limited to accredited investors. The public distribution is not a sale and therefore not a securities offering at all.

If your protocol is in the design phase and you want to pressure-test your structure before smart-contract development begins, write to info@oboluslaw.com. A scoped assessment of classification risk and licensing paths across the regimes relevant to your roadmap is faster and less expensive at the whitepaper stage than after launch.

At what point should a restaking protocol bring in specialised digital-asset counsel?

The optimal engagement point is during the architectural design phase, before core contracts are written and before any token distribution or fundraising. At that stage, a legal assessment can influence the protocol's feature set – whether governance is centralised or decentralised, whether fees accrue to a foundation or to token holders, whether receipt tokens are transferable or locked, whether validator selection is automated or curated. A protocol that builds without legal input and then tries to retrofit compliance after launch faces a much narrower set of options: the contracts may be immutable, the token may have already been distributed, and the protocol's marketing history may have created an investor expectation that cannot be unwound.

The engagement should cover three workstreams: classification (assessing the protocol and its token against the securities tests in the target jurisdictions), structuring (choosing the entity type, domicile, governance model, and token-sale mechanism), and documentation (preparing the whitepaper, prospectus or exemption notice, terms of service, and classification memo). In our DeFi and tokenization practice, we often see teams attempt to handle classification in-house, using articles or blog posts as guidance. That approach works for simple pure-utility tokens, but it fails for complex financial products like restaking protocols, where the classification turns on a multi-factor analysis that requires applying case law, regulatory guidance, and practical enforcement precedent.

A second engagement point is before any marketing or fundraising begins. If the protocol is conducting a private token sale to raise development capital, the sale must be structured under a securities exemption, the investors must be qualified, and the sale documentation must include appropriate risk disclosures and transfer restrictions. If the protocol is launching a public testnet or incentivised testnet where participants receive tokens, the distribution must be analysed to determine whether the tokens are securities (they usually are not, if testnet participation is genuinely open and tokens are earned for technical contributions, not purchased). If the protocol is airdropping tokens, the airdrop parameters – who qualifies, whether any payment is required, whether the airdrop is marketed as valuable – affect whether the airdrop is a securities offering.

A third engagement point is when the protocol encounters a regulatory inquiry or when an exchange requests legal opinions as a condition of listing the protocol's token. By that point, the protocol's classification is already a matter of record – the contracts are deployed, the token is in circulation, and the marketing claims are public. Counsel's job shifts from structuring to defense: preparing a response to the regulator, conducting a privilege review of internal communications, coordinating with the protocol's insurer (if any), and advising whether to apply for a licence retroactively or to attempt to exit the regulator's jurisdiction. That engagement is costlier, slower, and riskier than the design-phase engagement, because the protocol's options are constrained by what has already occurred.

For protocols that are post-launch but pre-enforcement, a retrospective classification audit is valuable. The audit examines the protocol's current operations, compares them against the design in the whitepaper, identifies any features or practices that increase classification risk, and recommends remediation steps – such as decentralising governance, removing profit-sharing mechanisms, or limiting the transferability of receipt tokens. The audit does not make the protocol's past activities compliant, but it can reduce future risk and improve the protocol's position if a regulator later opens an inquiry.

What cross-border tax and AML issues do restaking protocols face, independent of securities classification?

Even a restaking protocol that successfully argues it is not a security faces two separate compliance challenges: tax reporting and anti-money laundering. In the United States, staking rewards are taxable income to the recipient at the time they are "dominion and control" – generally when they are credited to the recipient's wallet or account. A restaking protocol that accumulates rewards in a pooled contract and distributes them later creates a timing question: is the income recognised when the protocol earns it (accrual), or when the user can withdraw it (realisation)? The IRS's position, as stated in Revenue Ruling 2023-14, is that staking rewards are income upon receipt, but "receipt" in the context of a protocol that auto-compounds rewards is ambiguous. Protocols that serve US users should consider issuing annual tax-reporting statements (similar to a 1099) showing the dollar value of rewards credited to each address, to reduce the risk that users underreport income and to position the protocol as cooperative with tax authorities.

In the European Union, staking rewards are generally subject to income tax in the member state where the taxpayer is resident. The rewards' character – income vs capital gain – depends on whether the taxpayer is staking as a business or as an investment. A restaking protocol that issues receipts tokens and then distributes rewards to those token holders may be treated as a dividend-paying entity for tax purposes, triggering withholding-tax obligations in some member states. If the protocol is domiciled in a member state with a broad tax treaty network (e.g., Malta, Luxembourg), it may be able to reduce or eliminate withholding tax, but that requires obtaining a tax ruling or a treaty-residency certificate in advance.

AML obligations apply to the protocol if it qualifies as a virtual-asset service provider under the FATF definition. A VASP is any entity or person that conducts, as a business, one or more enumerated activities: exchange between virtual assets and fiat, exchange between one form of virtual asset and another, transfer of virtual assets, safekeeping or administration of virtual assets or instruments enabling control, or participation in and provision of financial services related to an issuer's offer or sale of a virtual asset. A restaking protocol that accepts deposits, holds them in a pooled contract, and allows withdrawals is arguably conducting "safekeeping" and "transfer." If the protocol charges a fee and if it is operated by an identifiable entity or group, it is conducting that activity "as a business," and it is a VASP.

VASP status triggers customer due diligence obligations, transaction monitoring, suspicious-activity reporting, and the Travel Rule (the obligation to pass originator and beneficiary information with each transfer above a threshold, which varies by jurisdiction but is commonly USD 1,000 or EUR 1,000). The Travel Rule is particularly difficult for decentralised protocols to comply with, because it requires the protocol to identify and verify both the sender and recipient of every transfer. A protocol that does not perform KYC cannot comply with the Travel Rule, and a protocol that cannot comply with the Travel Rule cannot legally serve users in jurisdictions that enforce it (which now includes the EU under MiCA, the UK, Singapore, Hong Kong, Switzerland, and many others).

The practical path for protocols that want to remain permissionless is to geofence users in jurisdictions with strict AML enforcement, or to route users through a licensed intermediary that performs KYC and Travel Rule compliance on the protocol's behalf. The geofencing approach is the more common choice for early-stage protocols; the intermediary approach is adopted by protocols that scale and that see institutional demand. Neither approach is perfect. Geofencing can be evaded with VPNs and pseudonymous wallets. Intermediaries add cost, custody risk, and latency. The tension between permissionless infrastructure and AML compliance is one of the central design challenges in DeFi, and it is not yet resolved.

Related at OBOLUS

FAQ

Can a decentralised protocol be regulated?

Yes, if the protocol is not genuinely decentralised or if it was promoted, funded or controlled by identifiable persons during its launch phase. Regulators in the United States, the EU, and the major hubs treat a protocol as decentralised only when no person or group can unilaterally alter the system, when governance is exercised by a widely dispersed and unrelated set of participants, and when information is symmetrically available. Few protocols meet that standard at launch. If a protocol begins life with a core team, venture backing, and concentrated governance-token distribution, that launch phase is regulated. Decentralisation achieved later does not retroactively cure an unregistered securities offering or an unlicensed VASP operation that occurred before the protocol was decentralised.

Who is liable when a smart contract fails?

Liability turns on the relationship between the smart contract and the persons or entities that deployed, controlled, promoted or benefited from it. If a bug causes user losses and the contract was deployed by a legal entity (a foundation, a DAO LLC, a company), users will bring claims against that entity under contract law, tort law or the applicable consumer-protection or investor-protection statute. If the contract was deployed by individuals, those individuals are potentially personally liable unless they can demonstrate that they acted at arm's length, contributed only technical work with no economic interest, and made no representations about the contract's safety or functionality. Audits reduce but do not eliminate liability: an audit finding a contract "secure" does not mean the auditor guarantees user funds; it means the auditor found no vulnerabilities within the scope and methodology of the audit at the time it was conducted.

What wrapper suits this structure?

For a restaking protocol with a core team, meaningful treasury, and plans to raise venture funding, a Cayman Islands foundation company is the most widely adopted structure. It provides limited liability, tax neutrality, legal personality, and a clear home jurisdiction, without the governance overhead or fiduciary duties that a Swiss foundation carries. For a protocol that is decentralising from day one and that wants a legal wrapper that recognises DAO governance, a Marshall Islands or Wyoming DAO LLC is conceptually attractive, but case law is limited and the structure's acceptance by banks, exchanges and regulators is not yet proven. For a protocol that will operate entirely through immutable contracts, hold no treasury, employ no team, and conduct no marketing, the option is to operate without a legal entity – but that choice exposes every contributor to personal liability for regulatory violations and user claims.

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. We assess classification against the substance of rights, not the marketing label. For protocols building restaking infrastructure, the window to settle classification questions is before the first external capital commits. To map your protocol's exposure, contact info@oboluslaw.com.

By Roman Levitt, Technology & DeFi Counsel – specialising in DeFi protocol structuring, smart-contract legal frameworks, and token classification across the US, EU and Asia-Pacific hubs.

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