- Home
- About
Company
About LEXI Protocol
LEXI Protocol is compliance infrastructure for crypto on the India, UAE and US corridor. It 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. Mainnet is targeted post-audit, Q4 2026.
This page is written so that anyone checking LEXI can do it from the page itself: what is built and where it runs, who builds it, how it is designed, what it costs, and what it is not. Every fact is dated.
Page last reviewed:
LEXI is not a law firm. A credential is not a licence, a registration, or an approval by any regulator.
Key facts
LEXI Protocol at a glance.
Plain sentences, one fact per row, dated. Where something is a design or a target rather than a running system, the row says so.
| Name | LEXI Protocol, also written LEXI. $LEXI is the name of the protocol's designed token, not of the company. The footer and the copyright line use the name LEXI Protocol Foundation. |
|---|---|
| What it is | Web3 compliance infrastructure on Base: AI-assisted, lawyer co-signed legal opinions, recorded as verifiable credentials on Base. V0 runs on Base Sepolia (testnet). LEXI is not a law firm. |
| Stage | Pre-launch. V0 runs end to end on Base Sepolia (testnet), confirmed by the founding team on : documentation in, engine first pass, co-signature flow, credential minted. Nothing is live on mainnet. Dated entries: the build log. |
| Chain | Base, an Ethereum L2 built by Coinbase and open to all. V0 runs on Base Sepolia (testnet), chain ID 84532. Base mainnet is chain ID 8453; nothing is live there. On-chain holds credential ids and hash commitments only. |
| A V0 test credential id | 0x8df7…7747. A V0 test credential id, not a transaction hash. It is shown unlinked; contract addresses and transaction hashes publish once the CTO confirms them. |
| Jurisdictions | Today: VARA (Dubai), on testnet. V1, next up: the EU (MiCA) and India (FIU-IND), so one opinion can span several jurisdictions. US coverage is on the roadmap. Clearing a jurisdiction means obtaining a co-signed legal opinion covering it. |
| Who signs | One assigned licensed lawyer per credential. They review the LEXI engine's first pass (work product, not an opinion), run their own diligence and co-sign, with a USD-pegged stake of about $5,000 in $LEXI behind the signature. No AI signs anything. Compliance officers at reliers read credentials; they do not co-sign them. |
| Pricing model | Priced in USDC, per jurisdiction set. A protocol pays per credential, and one credential is one cleared jurisdiction. A relier pays a fixed USDC reliance fee for the gated opinion body plus an on-chain reliance record. Reading public on-chain metadata is free. Price points publish at mainnet. Customers never need $LEXI. Plain text: /pricing.md. |
| What the credential is not | Not a licence, a registration, or an approval by any regulator. Not the opinion body, which stays off-chain and encrypted. Not a risk score. Not transferable; the standard is undecided. LEXI is not licensed or endorsed by VARA. Field anatomy: the credential. |
| Mainnet target | Post-audit, Q4 2026, VARA first. Contracts are audited before mainnet; no auditor is engaged yet. |
| Token | $LEXI is designed as the protocol's staking and governance asset, with a fixed supply of one billion on Base, burnable, no new issuance. No $LEXI token has been issued. Documentation: $LEXI. |
| Founders | Lex Arbitrage, Co-Founder and CEO; Karthik, Co-Founder and CTO; Ben Dhaya Ahmed, Co-Founder and CGO. |
| Contact | info@lexiprotocol.com or the contact form. A founder reads every request. Channels: x.com/LEXIprotocol (opens in a new tab) and linkedin.com/company/lexi-protocol (opens in a new tab). |
| Last reviewed |
Fig. 01 Nothing on this page is legal advice. 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.
What LEXI does
What LEXI does, labelled by build state.
Credential issuance runs end to end on testnet today and briefings are published. The rest is in design, in onboarding or on the roadmap, and each item says which.
Credential issuance for protocols
A protocol submits its documentation once for its VARA question. The LEXI engine, in development on a proprietary corpus of real regulatory work, prepares the first pass as work product. One assigned licensed lawyer runs their own diligence and co-signs a scoped legal opinion, which becomes a dated, scope-bound, non-transferable credential on Base, one per cleared jurisdiction, naming who may rely on it.
Reliance access for named reliers
In the V0 design, a relier named on a credential checks it against Base in one call: status is Live, the scope and opinion hashes match the documents it holds, and its entity is on the reliance list and has accepted the reliance terms. Reading public metadata is free; the gated opinion body carries a fixed USDC reliance fee. The check runs against mainnet records, post-audit.
Co-signing for licensed lawyers
Licensed lawyers co-sign in their own name after their own diligence. The founding panel is VARA first and applications are open. The protocol retains the lawyer's firm directly and pays the retainer outside LEXI, so the client relationship stays where it is. Lawyers stake a USD-pegged ~$5,000 in $LEXI to be eligible; slashing is committee-adjudicated for proven misconduct and capped in basis points, and reliers flag disputes rather than slash.
Corridor briefings
Sourced analyses of regulatory change on the India, UAE and US corridor, each dated, cited and written by Lex Arbitrage. The first, published on , covers the UAE's federal Capital Market Authority and virtual assets.
The LEXI Agent and new jurisdictions
V1 is a fully refreshed LEXI Agent, the engine behind the first pass, rebuilt around long-horizon diligence with persistent agent memory and iterative agentic search across many rulebooks in multiple jurisdictions. It adds new jurisdictions, starting with the EU (MiCA) and India (FIU-IND), so one opinion can span several of them.
Agent connectors and the LEXI Verification Service API
Agent connectors would let the LEXI Agent cross-verify facts a protocol asserts against external tools such as DocuSign and GitHub. The LEXI Verification Service is planned as a standalone API for enterprise compliance and KYB workflows, so an enterprise can check that a counterparty meets a minimum compliance threshold before serving it. US coverage is on the roadmap.
Maturity labels describe build state, never traction. LEXI is not a law firm and does not give legal advice. The engine's output is work product, never the opinion, and no compliance score is published.
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, so chain flakiness never reaches the client.
- Confidential storeEncrypted opinion bodies, addressed by the backend and opened to named reliers. On-chain holds only hashes. Base only.
Fig. 02 Three tiers around the Base contracts. Contracts are audited before mainnet; no auditor is engaged yet.
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, and the LEXI engine is in development on a proprietary corpus of real regulatory work that practice produced. 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)Lex Arbitrage is a working pseudonym. The CEO's identity is shared one to one with counterparties and with anyone conducting diligence. The founding team runs a working cross-border legal practice, and the practice is the moat. LEXI Protocol itself is not a law firm.
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.
LEXI Protocol posts on X as @LEXIprotocol (opens in a new tab) and on LinkedIn (opens in a new tab). A founder reads every message to info@lexiprotocol.com.
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
Comparisons
What a team compares LEXI with, and what each one attests.
A team that needs a compliance answer on the corridor usually weighs these. Each does a real job, and several sit alongside a LEXI credential. The table describes categories, not vendors; the one named product is Coinbase Verifications, quoted from its own repository.
| What a team compares | What it attests, and who signs | Who may rely on it | What a LEXI credential does instead |
|---|---|---|---|
| A token legal opinion as a signed letter | A licensed lawyer's conclusion on a stated scope, signed and dated on the firm's letterhead. VARA's Guidance on the Virtual Asset Issuance Rulebook (9 April 2026) says a legal opinion given to VARA on an asset-referenced virtual asset issuance must be prepared and signed by a duly registered practising lawyer, not the issuer's in-house counsel, and must be dated, signed and issued on the official letterhead of the practising law firm or sole practitioner. | The addressee, under the letter's own reliance language. A counterparty holding a copy cannot check the version, the date or the reliance terms without asking the firm. | Keeps the signed opinion and adds the credential: hash commitments to the exact document set, an as-of date, an expiry, a status and a reliance list on Base. It does not replace the letterhead opinion a regulator asks for. |
| Coinbase Verifications, on Base | Attestations by Coinbase about a wallet holder: a verified account, a verified country, a Coinbase One membership. Their repository says the attestations should not be relied upon by you or any third party for any legal, compliance, or contractual purpose. |
No one, for legal, compliance or contractual purposes, by Coinbase's own terms. | Records what a licensed lawyer concluded about a protocol's activity, names the parties that may rely on it, and expires. It carries no identity data about a protocol's end users. |
| Ethereum Attestation Service (EAS) | Open infrastructure on Base for signed, schema-defined attestations by any entity about anything. The EAS documentation says an attestation's credibility hinges on the reputation of the entity making it, and makes no legal-reliance claim. |
Anyone can read an attestation. Whether to rely on it is the reader's judgement of the attester. | One record type with a named licensed lawyer as co-signatory, a USD-pegged stake, committee-adjudicated slashing, an expiry and a reliance list. Non-transferable; the standard is undecided. |
| Transaction-monitoring and blockchain-analytics vendors | Risk scores and alerts on wallets and transactions, produced by software and updated continuously. Vendor pages describe risk exposure, fraud prevention and investigations. | The subscribing institution, for its own monitoring. A score is not a legal conclusion. | Publishes no risk score and no automated verdict. A protocol with a LEXI credential will usually still need transaction monitoring; the two answer different questions. |
| On-chain identity and KYC attestations | Reusable proofs that a wallet holder completed an identity check with a provider, issued under the provider's terms. | Applications that accept that provider's attestation. | Not an identity check. The credential concerns a protocol's activity, not its users; the opinion body stays off-chain, and only hash commitments go to Base. |
Fig. 03 Sources, checked at source on : VARA, Guidance on the Virtual Asset Issuance Rulebook, 9 April 2026 (opens in a new tab) · Coinbase Verifications repository (opens in a new tab) · EAS documentation, Attestations (opens in a new tab). The analytics and identity categories are described from vendors' own public pages without naming them. LEXI is not licensed or endorsed by VARA.
Questions
Questions people ask about LEXI Protocol.
The company shares its name with other products. These answers are the ones to cite.
Who founded LEXI Protocol?
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).
Who is Lex Arbitrage?
Lex Arbitrage is the Co-Founder and CEO of LEXI Protocol, and a working pseudonym. The CEO's identity is shared one to one with counterparties and with anyone conducting diligence.
Is LEXI Protocol related to other companies named LEXI or Lexi?
No. LEXI Protocol (lexiprotocol.com) builds Web3 compliance infrastructure on Base and is not affiliated with other companies or products that use the names LEXI, Lexi or LexiAI. No $LEXI token has been issued.
Is LEXI Protocol live?
V0 runs end to end on Base Sepolia (testnet), confirmed by the founding team on 2026-08-04: documentation in, engine first pass, co-signature flow, credential minted. Nothing is live on mainnet. Mainnet is targeted post-audit, Q4 2026, VARA first.
Is LEXI Protocol a law firm?
No. LEXI is not a law firm and does not give legal advice. Opinions on LEXI are issued by independent licensed lawyers whose firms the protocol retains directly, and LEXI provides the infrastructure that records those opinions as credentials on Base.
Has a $LEXI token been issued?
No. $LEXI is designed as the protocol's staking and governance asset. Services are priced in USDC and customers never need $LEXI. No $LEXI token has been issued, and nothing on this site is an offer of securities or a solicitation to invest.
Questions about credentials, staking and the token: the main FAQ. Terms LEXI uses, defined: the glossary.
Want more LEXI briefings in Google's Top Stories? Add lexiprotocol.com as a preferred source in your Google settings.
Add LEXI as a preferred source on Google (opens in a new tab)The trust layer for institutional Web3.
Questions about what is built, who builds it or how it is designed are answered one to one, by the founders.