- Home
- For protocols
For protocols and token issuers
Multi-jurisdiction compliance for Web3 protocols, starting with VARA
DeFi, exchanges, RWA platforms, wallets. If your users sit in more than one jurisdiction, your compliance already does too. LEXI is built to turn that into one flow. On testnet today, the flow covers VARA (Dubai).
LEXI is not a law firm and gives no legal advice. A credential is not a licence, a registration, or an approval by any regulator.
Page last reviewed:
The old way
Counsel in sequence ends in a PDF nobody can check.
A project touching India, the UAE and the US today runs separate engagements on separate timelines, and gets memos that never cite each other. At the end, the output is a PDF opinion nobody downstream can verify without calling your lawyer. Your counterparties do not want your word for it. They want something they can check themselves.
What you get
One submission, a co-signed legal opinion, and a credential your counterparties verify.
One submission
Upload documentation once, pick your target jurisdictions, and work with an assigned licensed lawyer for each jurisdiction LEXI covers. Today, on Base Sepolia testnet, that flow covers VARA (Dubai). The EU (MiCA) and India (FIU-IND) are V1, next up, and one opinion can then span several jurisdictions. The full flow is on the how it works page.
A legal opinion, co-signed
A licensed lawyer runs their own diligence and co-signs a scoped, dated crypto legal opinion with a stake behind the signature. The credential carries no risk score, and no AI signs anything.
A credential that travels
The opinion is committed on Base as a verifiable credential naming your reliers: dated, scope-bound, non-transferable. Exchanges and other reliers check it themselves, in one call.
How it runs
From documents to credential, on testnet today.
- 01
Submit once
Upload documentation to encrypted storage and pick the jurisdictions you need.
- 02
The engine runs the first pass
Checklist, document review, risk read. The output is work product, not an opinion. No AI signs anything.
- 03
A licensed lawyer takes over
They review the work product, run their own diligence, and co-sign the legal opinion with a stake behind the signature.
- 04
The opinion becomes a credential
Dated, scope-bound, naming its reliers. Hash commitments go to Base, and reliers verify in one call.
AI-assisted, lawyer co-signed legal opinions, recorded as verifiable credentials on Base; the flow runs on Base Sepolia testnet today. The LEXI engine is in development on a proprietary corpus of real regulatory work.
See how it worksCoverage
The corridor, by build state.
One credential clears one jurisdiction. Clearing a jurisdiction means obtaining a co-signed legal opinion covering it (the glossary defines a cleared jurisdiction). The build log records what runs on testnet today.
| Jurisdiction | Regulators in scope | Build state | Version |
|---|---|---|---|
| UAE (Dubai) | VARA, and the federal CMA perimeter · VARA compliance (Dubai) | [On testnet] | V0 · Base Sepolia (testnet). Mainnet is targeted post-audit, Q4 2026. |
| EU | MiCA | [In development] | V1, next up |
| India | FIU-IND | [In development] | V1, next up |
| United States | Federal and state | [Planned] | On the roadmap, no date |
Fig. 01 Maturity labels describe build state, never traction. This roadmap describes intent. It is not a commitment to deliver any feature by any date, and nothing here should be relied on for a purchasing or investment decision. LEXI is not licensed or endorsed by VARA.
Pricing and early access
Priced in USDC, per cleared jurisdiction.
Protocols pay in USDC, per credential, and one credential clears one jurisdiction. Reliers pay a fixed USDC reliance fee to open the gated opinion body. Price points publish at mainnet. V0 runs on Base Sepolia testnet.
- Credential issuance, paid by the protocol
- USDC, per credential
- One credential
- one cleared jurisdiction
- Scope
- per jurisdiction set
- Reading public on-chain metadata, by anyone
- free
- Reliance access, paid by the relier
- fixed USDC fee
- Holding $LEXI
- never required
The co-signing lawyer is not paid from protocol revenue; the protocol retains the firm separately, outside LEXI. Plain-text copy: /pricing.md.
VARA first, on testnet.
V0 is VARA first, on Base Sepolia testnet. Early access means working through the flow with the founding team before mainnet.
- Early protocols get a say in the credential schema while it is still being locked.
- Nothing on testnet carries a charge, and no price point is published before mainnet. Until mainnet, nothing on testnet is a credential to rely on.
- Tell us what you are building and which jurisdictions you need. Your request lands with the founders directly, and the reply is one to one.
Questions
What protocols ask first.
Can one submission cover compliance in several jurisdictions?
That is what LEXI is built toward. LEXI is not a law firm and does not give legal advice. Today V0 covers VARA (Dubai) on Base Sepolia testnet: an assigned licensed lawyer runs their own diligence and co-signs, and the opinion becomes a credential on Base. The EU (MiCA) and India (FIU-IND) are V1, next up, when one opinion can span several jurisdictions.
Does a protocol need to hold $LEXI?
No. Services are priced in USDC, per cleared jurisdiction. Customers never need $LEXI. No $LEXI token has been issued.
How long does clearing a jurisdiction take?
LEXI's design target is about 5 days. Design target from complete documents, unmeasured. Sequential counsel on the corridor takes 8 to 12 weeks.
What does a protocol receive at the end?
A legal opinion co-signed by a licensed lawyer, and a credential on Base that records its firm ID, signatory, jurisdiction, as-of date, expiry, status, reliance mode, governing law, scope hash and opinion hash. The opinion body stays off-chain, encrypted, open to the reliers the credential names. A LEXI credential is not a licence, a registration, or an approval by any regulator.
The trust layer for institutional Web3.
V0 runs on Base Sepolia testnet; mainnet is targeted post-audit, Q4 2026.