On paper, drafting a token sale agreement in Lithuania looks like a localized document exercise. In practice, the document is the legal architecture of your offering — and a drafting error can convert a product launch into an unregistered securities offering under Lithuanian and EU law. Lithuania operates under the MiCA (Markets in Crypto-Assets Regulation) regime supervised by the Bank of Lithuania, which means token classification, disclosure obligations and cross-border sale mechanics must all be resolved before a single agreement is signed. This page explains how the process works, where operators most commonly go wrong, and what a properly structured token sale agreement must accomplish.
Why the token sale agreement is the offering, not just the paperwork
The agreement is not a formality that follows the commercial decision — it encodes the commercial decision in legally binding terms. Every right the token purchaser acquires, every restriction on transferability, every condition on refund, every representation about the project's status: all of it is captured there. Under the MiCA regime administered by the Bank of Lithuania, the regulatory classification of a token turns on the substance of those rights, not on the label the issuer attaches to them. A token that carries profit expectations tied to the issuer's efforts will attract the scrutiny that an asset-referenced token or a security would attract, regardless of what the agreement's header calls it.
That single fact — that classification follows substance — is the central risk for any issuer preparing a sale in Lithuania. In our cross-border practice, we regularly see issuers who have spent significant time and capital on a whitepaper and a marketing plan before commissioning the legal documents. By that stage the commercial terms are largely fixed, and the agreement must accommodate them. When those commercial terms have inadvertently created security-like rights, the available remedies are expensive. Catching the issue at the term-sheet stage, before the agreement is drafted, is structurally far cheaper.
To discuss the classification and drafting requirements for your specific token structure, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts — the entity, the user base, the banking — change the analysis. Map your options.
Token classification under MiCA and Lithuanian law: how it works in practice
Under the MiCA regime, every token offered to the public in the EU/EEA falls into one of three categories — an asset-referenced token (ART), an e-money token (EMT), or a residual "other crypto-asset" — and the obligations imposed on the issuer differ materially depending on that classification. The Bank of Lithuania, as the national competent authority for MiCA purposes in Lithuania, supervises compliance and authorisation for issuers registered or seeking to reach EU purchasers from a Lithuanian entity.
The classification analysis starts with the rights the token confers. Does the holder have a claim on the issuer's assets or revenues? Does the token appreciate in value primarily because of the issuer's managerial efforts? Does it entitle the holder to a distribution? Each of these features, individually or in combination, shifts the token toward a more heavily regulated category. Conversely, a token that functions purely as access to a defined service — with no secondary-market price driver tied to the issuer — may qualify as a straightforward "other crypto-asset" subject to a lighter regime, including a whitepaper notification rather than a full authorisation.
The practical consequence for agreement drafting is significant. An agreement for an "other crypto-asset" must still address purchase mechanics, jurisdiction, consumer protections and AML obligations — but it does not carry the reserve management, redemption and capital requirements that attach to an ART or EMT. Getting this classification right at the outset determines the shape of the entire legal stack.
A common assumption we encounter is that a utility label on the whitepaper settles the classification. It does not. The Bank of Lithuania and ESMA assess substance. An agreement that describes what the token does but fails to define what the token cannot do — in terms of profit rights, governance weight or redemption claims — leaves interpretive space that regulators will fill against the issuer. The drafting task is to close that space deliberately.
What a compliant token sale agreement in Lithuania must contain
A token sale agreement that operates under the MiCA regime and satisfies Lithuanian commercial law requirements must address at least seven structural matters, each of which carries its own drafting risk.
Identification of the parties and the issuer's regulated status. The agreement must identify whether the issuer is a Lithuanian-incorporated entity, a foreign entity selling into Lithuania or to Lithuanian-based purchasers, or an entity relying on a third-country exemption. The MiCA passporting regime — under which a CASP (crypto-asset service provider) authorised in one member state may operate across the EU/EEA — creates cross-border sale mechanics that must be reflected in the governing-law and submission-to-jurisdiction clauses.
Token description and classification statement. The agreement must describe the token in terms consistent with the whitepaper and with the regulatory classification. Inconsistency between the agreement and the whitepaper creates a disclosure risk. The classification statement should be drafted as a factual representation, not a warranty of regulatory outcome.
Purchase mechanics and payment terms. Lithuanian AML obligations apply to the receipt of funds in connection with a token sale. The agreement must specify the permitted payment methods, the AML/KYC conditions precedent to completion, and the issuer's rights to decline or reverse a purchase on AML grounds. The Travel Rule — the obligation under FATF Recommendation 15 to pass originator and beneficiary data with a virtual asset transfer — may apply where the consideration itself is a virtual asset.
Allocation, vesting and lockup terms. Where the token carries a vesting schedule or a lockup period, the agreement must state the conditions clearly. Vesting and lockup mechanics are also relevant to the classification analysis — a long lockup combined with a profit expectation can move a token closer to a security-like instrument.
Representations and warranties. The issuer's representations about the project's development status, the whitepaper's accuracy and the token's regulatory status must be calibrated carefully. Over-representing the project's development stage is a material misrepresentation risk. Under-representing it creates product-launch issues. We advise drafting these as present-state representations with an explicit carve-out for forward-looking statements.
Restriction on transfers and secondary sales. Where the issuer intends to restrict secondary-market trading — either as a regulatory precaution or as a commercial matter — the restriction must be drafted with precision. Vague restrictions are unenforceable. A restriction that captures transfers to affiliates may unintentionally prevent intra-group liquidity management.
Governing law, dispute resolution and jurisdiction. For a Lithuanian entity selling to purchasers across the EU/EEA, the governing-law analysis is non-trivial. Lithuanian law as the law of the issuer's domicile is a defensible choice for B2B sales. For sales involving retail participants — even incidentally — EU consumer-protection rules impose mandatory overrides that a governing-law clause cannot contract out of.
Cross-border considerations: banking, tax and structural interaction
A Lithuanian token sale agreement does not operate in isolation. The issuer's banking relationships and tax position create legal obligations that the agreement must either address directly or acknowledge through representations.
Lithuanian-incorporated entities typically bank with EU-based credit institutions. Those institutions apply their own enhanced due diligence to token sale proceeds. An agreement that lacks credible AML/KYC conditions precedent — or that allows anonymous or pseudonymous purchasers — will often trigger a bank's unilateral hold on incoming funds. In our practice, we have seen token sale proceeds frozen at the issuer's bank because the sale agreement was signed before the banking relationship had been stress-tested against the sale mechanics. The agreement and the banking documentation should be reviewed together.
The tax interaction is equally material. The VAT treatment of token sale proceeds in Lithuania — and, by extension, across the EU under the destination-country principle — depends on whether the token constitutes consideration for a supply of services, a financial instrument, or neither. A token that is pre-payment for a future service may be treated differently from a token that represents an investment right. The agreement's characterization of the token will influence the VAT analysis, which in turn affects whether VAT must be charged, collected and reported at the time of sale or deferred to delivery of the service.
For issuers with a cross-border corporate structure — a holding entity in a non-EU jurisdiction and a Lithuanian operating entity — the intercompany arrangements must align with the sale agreement. A token issued by the holding entity but sold through the Lithuanian entity creates transfer-pricing and permanent-establishment questions that should be resolved before the agreement is finalized.
If your token sale involves cross-border corporate structure, banking due diligence or VAT exposure, write to OBOLUS at info@oboluslaw.com. If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. Map your options.
Does a MiCA whitepaper change the drafting of the agreement?
Yes — and the interaction runs in both directions. Under the MiCA regime, a whitepaper published in connection with a token offering creates disclosure obligations whose scope depends on the token category. For "other crypto-assets" offered to the public, the whitepaper must be notified to the Bank of Lithuania before publication. For ARTs and EMTs, the issuer requires prior authorisation. The agreement must not contradict the whitepaper, and where the whitepaper makes representations about the token's functionality or the project's roadmap, the agreement's representations clause should be drafted to incorporate or cross-reference those statements by design.
The practical workflow we advise is to draft the term sheet, then run the classification analysis, then draft the whitepaper and the sale agreement in parallel, with the classification analysis as the shared input. Drafting the agreement after the whitepaper is published — without the classification analysis as a shared foundation — creates consistency risk. We have seen issuers publish a whitepaper describing the token in terms that imply security-like rights, then attempt to draft a sale agreement that characterizes the same token as a utility instrument. The inconsistency, when identified by the Bank of Lithuania or by a purchaser's counsel, creates liability for both.
The whitepaper also affects the agreement's marketing restrictions clause. MiCA imposes specific requirements on how token offerings may be marketed to EU residents — requirements that are independent of the sale agreement but that must be consistent with it. An agreement that grants the issuer broad rights to amend the sale terms after publication, without a corresponding whitepaper update obligation, may breach the regime's disclosure continuity expectations.
How the process works: a cross-border token sale in practice
In a recent matter, a technology company incorporated outside the EU sought to sell a utility token from its Lithuanian subsidiary to purchasers across the EU/EEA. The initial draft agreement had been prepared without a prior classification analysis and contained a profit-sharing mechanism tied to platform revenue — a feature that, under the MiCA regime, triggered ART-adjacent concerns. The Bank of Lithuania, reviewing the whitepaper notification, identified the inconsistency between the agreement's profit-sharing terms and the whitepaper's description of the token as a utility instrument.
We were engaged after the notification had been submitted but before the Bank of Lithuania had issued its formal response. Working through the classification analysis, we identified two paths: restructure the profit-sharing mechanism to remove the revenue-linkage, or reclassify the token and proceed under the ART authorisation pathway. The client chose the former. We redrafted the sale agreement, revised the whitepaper, and coordinated the resubmission. The Bank of Lithuania accepted the revised notification within a matter of weeks. The sale proceeded on schedule. The critical lesson was that the agreement and the whitepaper must be designed as a single legal document set — not as sequential deliverables.
Self-assessment: is your token sale agreement ready to sign?
Before executing a token sale agreement in Lithuania, an issuer should be able to confirm each of the following.
First: a written classification analysis exists, prepared by counsel, that addresses the token's rights against the MiCA taxonomy. The analysis should address what the token does not confer as explicitly as what it does.
Second: the sale agreement and the whitepaper have been reviewed for consistency by the same counsel. Any representation in either document that is not mirrored — or deliberately excluded — in the other should be a deliberate drafting choice, not an oversight.
Third: the AML/KYC conditions precedent in the agreement are operational. The issuer's compliance program — including Travel Rule obligations for virtual-asset consideration — must be capable of performing the checks required before completion.
Fourth: the banking relationship has been stress-tested against the sale mechanics. The issuer's account-holding bank should have reviewed the transaction structure before the agreement is signed, not after the first tranche of proceeds arrives.
Fifth: the governing-law and jurisdiction clause has been reviewed against the purchaser profile. A clause that is appropriate for professional investors in Lithuania may expose the issuer to mandatory consumer-protection overrides if the purchaser base includes retail participants in other EU member states.
Sixth: the cross-border corporate structure — if any — has been aligned with the agreement. The entity that signs the agreement should be the entity that holds the relevant regulatory status, banking relationship and tax registration.
If any of these six points cannot be confirmed with confidence, the agreement is not ready to sign.
Related at OBOLUS
- Token offerings and securities law for digital-asset businesses – full practice overview covering classification, issuance and cross-border compliance
- Stablecoin issuance authorisation for institutional clients – ART and EMT authorisation under MiCA, from structure to Bank of Lithuania notification
- VAT treatment of crypto services in Switzerland – cross-border tax context for EU-adjacent token structures and Swiss entities
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 — and we advise operators across more than seventy licensing jurisdictions who need that distinction to hold in a regulatory examination. To discuss your token sale structure, contact info@oboluslaw.com or reach us at t.me/oboluslaw.
FAQ
Is my token a security?
Token classification under the MiCA regime and applicable Lithuanian law turns on the substance of rights the token confers — not its label. A token that carries profit expectations tied to the issuer's efforts, a claim on revenues, or governance rights analogous to equity will attract heightened scrutiny. Classification requires a written analysis against the MiCA taxonomy and, where relevant, the securities law of each jurisdiction into which the token is offered. OBOLUS conducts that analysis before drafting begins.
Do I need a MiCA whitepaper?
For most public token offerings in the EU/EEA, yes. Under the MiCA regime, "other crypto-assets" offered to the public require a whitepaper notified to the Bank of Lithuania before publication. Asset-referenced tokens and e-money tokens require prior authorisation. Certain exemptions apply — for example, offerings limited to qualified investors or below a defined transaction threshold — but those exemptions must be confirmed by reference to the applicable regime, not assumed. The whitepaper must be consistent with the sale agreement.
How should an airdrop be structured legally?
An airdrop is not automatically exempt from the MiCA regime or Lithuanian AML obligations simply because no monetary consideration is exchanged. If the tokens distributed have economic value and the recipients acquire transferable rights, the distribution may constitute a public offering. The AML/KYC obligations that apply to token sales can also apply to airdrops where the issuer collects wallet addresses and personal data. Structuring an airdrop legally requires a classification analysis, a review of the distribution mechanics, and a confirmed position on AML applicability.
By Roman Levitt, Technology & DeFi Counsel — specializing in token classification, smart-contract legal review and the regulatory treatment of decentralized protocols across the EU and cross-border jurisdictions.
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.