How exchanges verify a token legal opinion

KuCoin's Guidelines on the Legal Opinion Required for Projects to Launch on KuCoin are undated on their face. The PDF's metadata is dated 7 May 2020, and the file is still linked from the listing page updated 16 December 2025. Whether its firm-tier, headcount and founding-date bars are applied in 2026 is not published, and nothing here suggests a LEXI co-signing firm would meet them. What the guidelines are useful for is different: they are a written list of what a listing team checks once a PDF opinion lands. Five of the articles map to a field or a flow on the credential.

Art. 7 · form, signature, letterhead, seal, date of issue

The signatory and the firm ID are public on-chain fields, and the as-of date is recorded at signature. A relier reads them without asking anyone.

Art. 8 · no modification after signing; changes by a separate complementary opinion

Nothing is edited after signing. A refreshed opinion is a new credential, a re-issue with its own date, and the old one is left to expire or is revoked.

Art. 11 · the white paper annexed as the version the opinion covers

The scope hash binds the exact document set. If a document changes, the hash stops matching, and the second step of the check fails.

Art. 17 · a clear security or not-security conclusion, not linguistically ambiguous

The conclusion lives in the opinion body, off-chain, encrypted and gated to named reliers. No score, rating or verdict goes on-chain.

Art. 19 · the issuer or the firm authorises KuCoin to use the opinion, or places no restriction on third-party reliance

Reliance mode and the named-relier list say who may rely; a reliance record shows that the relier accepted the terms, on a date.

The firm-tier and headcount tests have no on-chain equivalent by design: whether a firm clears a relier's bar is the relier's own call.

A closing opinion speaks as of its date.American Bar Association, Business Law Section, Core Opinion Principles, section 4.1 (2017)

The Core Opinion Principles go on: the opinion giver has no obligation to update a closing opinion for later events or legal developments (section 4.1), and the opinion may be relied on only by its addressee and any other person expressly authorised to rely (section 4.2). A recipient is also not entitled to rely on an opinion it knows to be incorrect (section 1.4). These are 2017 principles, and the practice behind them is older.

A 2021 article in the American Bar Association's Real Property, Trust and Estate Law Section journal Opinions Matters describes how firms handle the parties who were not addressed. Unless the letter says otherwise, only the recipient named in it may rely. Where a firm allows a later party to rely, it generally limits that party to the rights the original addressee had, and only as of the original date. Recipients often ask that an opinion may be delivered to a party without that party being entitled to rely on it; reliance matters to the giver because it generally creates a duty of care.

For a listing team this means three things. A PDF that looks current is only dated; its date is the fact. A reliance letter is a second negotiation, and it may come back limited to the original date or marked as delivered but not to be relied upon. And a bring-down is a new letter with a new date, which restarts the same checks on the same file.

VARA (Dubai, outside DIFC) licenses VASPs per activity under rulebooks. Part VIII of the Market Conduct Rulebook (version of 19 May 2025) requires every VASP to set standards for the virtual assets it services, to run due diligence before and at all times during the activity, to publish those standards on its website, to keep the assessment records for eight years, and to notify VARA as soon as possible when an asset no longer meets the standards. The factors include securities-law exposure, any regulatory approvals the asset holds, and the issuer's background. One published example: CoinMENA's VA Standards (undated) commit the exchange to understand and document the regulatory treatment of each asset by VARA and other relevant authorities.

Part IV of the Broker-Dealer Services Rulebook (same version) is the heavier file, and it belongs to the Licensed Distributor, the VASP through which a Category 2 issuance is placed. The distributor must ensure the quality of each issuer and asset beyond all reasonable doubt (Rule IV.B.1), run comprehensive due diligence on both (IV.B.3 and IV.B.4), and submit to VARA the white paper, the risk disclosure statement, a signed compliance declaration and its due-diligence reports (IV.D.1), after which a fifteen Working Day Submission Period runs (IV.D.2). VARA is never deemed to have approved an asset by virtue of that submission (IV.D.7). Two rules speak directly to staleness: the diligence must stay up to date and accurate at all times (IV.E.1), and on any material change the distributor must redo it and resubmit (IV.E.3).

Note what the Category 2 package does not contain. VARA does not require a legal opinion in it; it requires comprehensive audits of all smart contracts used for the asset, with findings remediated (IV.B.3(e)). The one VARA text that names who may sign a legal opinion is narrower still: its Guidance on the Virtual Assets Issuance Rulebook (9 April 2026) covers an asset-referenced virtual asset issuance under Annex 2, and there it expects the issuer to keep that opinion current and to supply a revised or supplemental opinion after a material change. A co-signed opinion with an as-of date, a scope hash and a Live, Expired or Revoked status is evidence a distributor can file and re-check under IV.E.1 and IV.E.3. VARA does not ask for it.

Clearing a jurisdiction, in LEXI's vocabulary, means obtaining a co-signed legal opinion covering that jurisdiction. The VARA track as a whole is on VARA compliance (Dubai); the regulator events since 2024, each with what it does to an opinion's scope or date, are in the corridor tracker.

The EU (MiCA) is V1, next up, for LEXI; nothing below is live coverage. It is here because a listing team at an EEA venue runs a parallel check, and MiCA puts the gatekeeping on the platform rather than on an opinion. Before admitting a crypto-asset to trading, a platform operator must assess the suitability of the asset (Article 76(2)), including the reliability of its technology and any link to illicit or fraudulent activity, taking into account the experience, track record and reputation of the issuer and its development team. For an ordinary crypto-asset, the white paper notification carries an explanation of why the asset is not an excluded asset, an e-money token or an asset-referenced token (Article 8(4)); that is an explanation, not a legal opinion, and the regulation does not say who writes it. MiCA asks for a legal opinion only for asset-referenced tokens (Articles 17(1)(b)(ii) and 18(2)(e)).

Two public lists matter to a relier on this side of the corridor: ESMA's interim MiCA register of authorised crypto-asset service providers, and its register of non-compliant entities. Both move weekly, so any check records its snapshot date; the snapshot read for this briefing was 7 October 2026. Kraken's EEA rule, above, shows how a venue turns Article 76 into a file. When V1 reaches MiCA, the credential's as-of date is what a relier compares with the register row and with the white paper's notification date. Until then, this section describes a check other people run.