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. Every participant carries a LEXI ID, a unique 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 an encrypted store, not on-chain. Only hash commitments ever touch the chain, which is what lets the system honour deletion and erasure requests under laws like India's DPDP Act and the GDPR.

Step 2. The engine runs the first pass

A fine-tuned engine, in development on a proprietary corpus of real regulatory work, monitors each selected jurisdiction. It builds the compliance checklist for your case, checks your documentation against it, and produces an internal risk read.

All of this output 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 human who owns the judgment. No AI signs anything at LEXI.

Step 3. A licensed professional takes over

A qualified legal professional, assigned to your engagement and staked to participate, reviews the work product, runs their own diligence, and co-signs the legal opinion. The signature is theirs alone: a credential can only mint against the signatory's own signature, and signing keys never leave the signatory.

The professional's firm is retained by your project directly, the way legal engagements already work. LEXI coordinates the flow; it does not sit between you and your counsel. More on the professional's side of the table on the legal professionals page.

Step 4. The opinion becomes a credential

The core contracts verify the co-signed attestation and mint a credential on Base, one per cleared jurisdiction. "Cleared" here means exactly this: a licensed professional has co-signed a scoped legal opinion covering that jurisdiction. The credential is dated, scope-bound, non-transferable, and it names who may rely on it.

On-chain, the credential carries the firm, the signatory, the jurisdiction, the dates, the status, the reliance mode, the governing law, and hash commitments that bind the exact opinion text. The opinion body itself stays off-chain and encrypted, readable by the credential's named reliers. Anyone you name can verify the credential on-chain in a single call.

What happens after

• Reliance is explicit. A relier accepts the reliance terms before reliance attaches, and each reliance is recorded on-chain. By default the professional whitelists who may rely (Selective mode).
• Status is live. A credential reads Live, Expired, or Revoked. Counterparties always see the current state, not a stale PDF.
• Disputes have a path. Reliers can flag a dispute. A committee adjudicates it, and a professional's stake can be slashed for proven misconduct. Nobody slashes anybody unilaterally.