How LEXI works: from documentation to on-chain credential

Step 1. Submit once, pick your jurisdictions

You open an engagement on the LEXI portal, upload your documentation to encrypted storage, and select the jurisdictions you want covered. Today, on Base Sepolia testnet, that means VARA (Dubai); the EU (MiCA) and India (FIU-IND) are V1, next up. Every participant carries a LEXI ID, an on-chain identity, so the engagement has named parties from the start. An engagement is a workspace shared by your team and the assigned firm; either side can open one and invite the other.

Your documents live in the encrypted confidential store, not on-chain. Only hash commitments ever touch the chain, which is what lets the store honour deletion and erasure requests under laws such as India's DPDP Act and the GDPR.

Step 2. The engine runs the first pass

The LEXI engine, in development on a proprietary corpus of real regulatory work, works from each selected jurisdiction's rulebooks. It builds the compliance checklist for your case, checks your documentation against it, and produces an internal risk read. That output is the engine first pass.

All of it is work product. It is never the opinion, it never goes on-chain as a verdict, and there is no published compliance score. Anything the engine is not confident about routes to the lawyer who owns the judgment. No AI signs anything at LEXI.

Step 3. A licensed lawyer takes over

One licensed lawyer, assigned to your engagement and staked to co-sign, reviews the work product, runs their own diligence, and co-signs the legal opinion. The opinion is theirs. The stake is USD-pegged, about $5,000 in $LEXI, with a 14-day unbonding period. No $LEXI token has been issued.

The lawyer's firm is retained by your project directly, outside LEXI, the way legal engagements already work. LEXI coordinates the flow; it does not sit between you and your counsel, and none of LEXI's revenue goes to the co-signing lawyer. Compliance officers at the parties that rely on the opinion read the credential; they do not co-sign it. More on the lawyer's side of the table on the legal professionals page.

Step 4. The opinion becomes a credential

The co-signed opinion is recorded on Base as a credential, one per cleared jurisdiction. "Cleared" means exactly this: a licensed lawyer has co-signed a scoped legal opinion covering that jurisdiction. It is not a licence, a registration, or an approval by any regulator. LEXI is not licensed or endorsed by VARA. The credential is dated, scope-bound and non-transferable (the exact token standard is undecided), and it names who may rely on it.

On-chain, the credential carries the firm ID, the signatory, the jurisdiction, the as-of date and expiry, the status, the reliance mode, the governing law, and the scope and opinion hashes that bind the exact text. The opinion body stays off-chain and encrypted, readable by the reliers the credential names. Anyone you name can verify the credential on-chain in one call. On testnet today every credential is a test record; nothing is live on mainnet, and contract addresses publish once the CTO confirms them.

How long it takes

Sequential counsel on the corridor takes 8 to 12 weeks, one engagement after another. LEXI's design target is about 5 days. Design target from complete documents, unmeasured. Your own timeline depends on your documentation and the jurisdiction.