A licensed lawyer's opinion,
verifiable on Base.
LEXI turns a licensed lawyer's co-signed legal opinion into a dated, scope-bound credential on Base that the parties it names can verify in one call. VARA first, running on Base Sepolia testnet today; the EU (MiCA) and India (FIU-IND) are V1, next up.
Licensed to practice? Apply to co-sign
Build logMainnet target moved to post-audit, Q4 2026
LEXI is not a law firm. A credential is not a licence, a registration, or an approval by any regulator.
- Jurisdiction
- AE · VARA (Dubai)
- Governing law
- Dubai (onshore UAE)
- As-of
- dated at signature
- Expiry
- bound by scope
- Reliance
- Selective · named reliers
- Firm ID
- lexi:firm:0x0000
- Scope
- Whether the activities described in the submitted documentation require a VASP licence under the VARA framework. Tax and employment matters excluded.
- Scope hash
- 0x0000…0000
- Opinion hash
- 0x0000…0000
0x0000…0000
- 01Status is Live, not Expired or Revoked
- 02Scope and opinion hashes match the documents you hold
- 03You are a named relier and have accepted the terms
What runs on testnet today
Build state build log
V0 end to end on Base Sepolia (testnet), confirmed by the founding team · documentation in, engine first pass, co-signature flow, credential mintedThe corridor
Three rulebooks that do not talk to each other.
A project touching India, the UAE and the US has to satisfy three regulators. Counsel in sequence takes 8 to 12 weeks and ends in a PDF nobody downstream can verify. LEXI clears one jurisdiction at a time, and clearing one means obtaining a co-signed legal opinion covering it, recorded as a credential the named parties check themselves.
- [V1 · next up]FIU-INDIndia
- [V0 · on testnet]VARA (Dubai)UAE
- [Planned]Federal and stateUS
Fig. 01 The corridor. One credential per cleared jurisdiction; the line leaves through the gate, VARA first. MiCA (EU) joins FIU-IND in V1.
How it works
From documents to credential, in one flow.
- 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. One assigned licensed lawyer co-signs each credential.
See how it worksThe credential
One opinion, three layers of disclosure.
The on-chain record holds hashes and metadata. The opinion body stays off-chain, encrypted, open to the reliers the credential names. Non-transferable; the token standard is undecided. No risk score is written on-chain.
A LEXI credential is a co-signed legal opinion committed on-chain. It is not a licence, a registration, or an approval by any regulator. LEXI is not licensed or endorsed by VARA.
- firm ID
- signatory
- jurisdiction
- as-of date
- expiry
- status: Live / Expired / Revoked
- reliance mode: Open / Selective
- governing law
- scope hash
- opinion hash
- scope text
- assumptions and reservations
- permitted-use terms
- the opinion body, encrypted
- EU-hosted confidential store
- opened against an on-chain reliance record
Their README says the attestations should not be relied upon for any legal, compliance, or contractual purpose
.
Names the parties that may rely on it, carries a licensed lawyer's signature, and expires.
Fig. 02 The credential, on-chain and off-chain. Field list is the V0 target schema.
For exchanges, VASPs and Licensed Distributors
Read a credential in three steps.
Status is Live, not Expired or Revoked.
As-of date, expiry and revocation are on-chain.Does it still speak as of a date I accept?
The scope and opinion hashes match the documents you hold.
Hash the PDF and the scope text and compare them with the on-chain commitments.Is this the document the lawyer signed?
Your entity is a named relier and has accepted the reliance terms.
The credential names who may rely on it; the reliance record shows you accepted the terms.Am I expressly authorised to rely?
- Reading public on-chain metadata
- free
- Reliance access: the gated body plus an on-chain reliance record
- fixed USDC fee
- Credential issuance, paid by the protocol
- USDC, per credential
- One credential
- one cleared jurisdiction
- Holding $LEXI
- never required
LEXI has not issued a token and is not a listing agent. If you are an exchange, you are a relier: here is how a credential is read.
Who it is for
Four ways in.
Read a credential, free.
The three-step check in a listing team's language, and the design-partner relier structure on Base Sepolia.
/exchanges/ → For protocols and token issuersA co-signed legal opinion, VARA first.
One submission, one co-signed legal opinion, and a credential your counterparties verify themselves. V0 covers VARA (Dubai) on Base Sepolia testnet.
/protocols/ → For licensed lawyersCo-sign. Keep your client and your standards.
You run your own diligence and the signature is yours. A USD-pegged stake of about $5,000 in $LEXI stands behind it; disputes go to a committee, and reliers cannot slash.
/legal-professionals/ → For anyone doing diligenceRead the key facts.
What is built, where it runs, the team, the architecture, the roadmap and the economics. Dated, in raw HTML.
/about/ →What is true today
What is true today: a working cross-border legal practice, a proprietary corpus of real regulatory opinions, and a warm pipeline. V0 is live on Base Sepolia (testnet), end to end: documentation in, engine first pass, co-signature flow, credential minted. Nothing is live on mainnet yet, and this page will say so until it is.
- Client-side frontendProtocols, firms and signatories sign their own transactions. The client holds no infrastructure credentials.
- EU-hosted backendSelf-hosted in the EU. Relays signed transactions and owns gas, nonces and retries.
- Confidential storeEncrypted opinion bodies, addressed by the backend. On-chain holds only hashes. Base only.
Fig. 03 Three tiers around the Base contracts. Contracts are audited before mainnet; no auditor is engaged yet.
Roadmap
V0, V1, V2.
Opinion issuance as an on-chain credential
End-to-end opinion issuance as an on-chain credential, VARA (Dubai) first, on Base Sepolia (testnet). Mainnet is targeted post-audit, Q4 2026.
A refreshed LEXI Agent and new jurisdictions
Long-horizon diligence, persistent agent memory, iterative agentic search across many rulebooks. New jurisdictions starting with the EU (MiCA) and India (FIU-IND), so one opinion can span several.
Connectors and a verification API
Agent connectors (DocuSign, GitHub) to cross-check protocol-asserted facts, and a standalone LEXI Verification Service API for enterprise compliance and KYB. US coverage is on the roadmap.
Protocol USDC revenue, as designed.
Services are priced in USDC. Customers never need $LEXI. No $LEXI token has been issued. $LEXI documentation
Team
Built by the founding team.
LEXI Protocol was co-founded by Lex Arbitrage (Co-Founder and CEO), Karthik (Co-Founder and CTO) and Ben Dhaya Ahmed (Co-Founder and CGO). The founding team runs a working cross-border legal practice; LEXI Protocol itself is not a law firm.
Lex Arbitrage
Corridor strategy and protocol design: which opinion, which jurisdiction, which lawyer signs.
@lex_arbitrage (opens in a new tab)Karthik
Three-time founder. Co-founded Spicenet, whose $3.4M seed in December 2024 was led by Hack VC and Magnus Capital. Builds derivatives exchanges, multi-asset risk engines and market-making systems.
@implied_vol (opens in a new tab)Ben Dhaya Ahmed
Growth, partnerships and ecosystem across Europe, the Middle East and emerging markets.
Who we are, what runs on testnet today and how engagements work: Read the key facts
Latest
Dated, so you can watch the build.
Compliance, made portable. Regulation, made programmable.
The trust layer for institutional Web3.
Relier, press or diligence? Talk to us