Dated entries on what LEXI runs on Base Sepolia (testnet), what is in progress and what is next. Each entry carries a date, a label and an author, and says why anything is delayed. Newest first.
Nothing is live on mainnet. Every entry on this page describes Base Sepolia (testnet) unless it says otherwise.
Page last reviewed:
What runs today
LEXI's V0 prototype runs end to end on Base Sepolia, Base's public testnet (chain ID 84532): a protocol submits documentation, the LEXI engine produces a first-pass work product, a co-signature flow runs, and a credential is recorded on-chain as a 32-byte credential id with hash commitments. The flow was confirmed end to end on 2026-08-04. Nothing is live on Base mainnet; mainnet is targeted post-audit, Q4 2026, VARA first.
Network facts Base
Base Sepolia (testnet)chain ID 84532 · RPC https://sepolia.base.org · explorers sepolia.basescan.org and base-sepolia.blockscout.com · source: Base docs, connect to Base (opens in a new tab)
Base mainnetchain ID 8453 · nothing is live on mainnet
Why Base SepoliaBase Sepolia received the Azul upgrade on 20 April 2026, about five weeks before Base mainnet (28 May 2026, per Base's own upgrade page), so the testnet carries each network change first and V0 is tested against it before mainnet. · source: Base docs, Azul overview (opens in a new tab)
V0 contractsDeployed on Base Sepolia (testnet). · addresses and explorer links publish once the CTO confirms them
Fig. 01 Network facts as published by Base. Explorer links follow address confirmation; until then no address or transaction hash appears on this site.
The log, newest first
· PlannedLex Arbitrage
Mainnet target moved to post-audit, Q4 2026
Mainnet is now targeted post-audit, Q4 2026, VARA first. The earlier public target was a fixed week in late October 2026. Hardening and a security audit come before any mainnet deployment, and no auditor is engaged yet, so the date now follows the audit rather than the calendar.
The status line on every page reads: PRE-LAUNCH · V0 LIVE ON TESTNET · MAINNET TARGETED POST-AUDIT, Q4 2026. Nothing is live on mainnet, and this page will say so until it is.
· DecisionLex Arbitrage
Co-signers are licensed lawyers only
From this date a legal professional on LEXI means a licensed lawyer. Compliance officers do not stake and do not co-sign, and no page on this site lists them as a co-signer type. They still appear where they belong: as the people at exchanges and other reliers who read credentials.
One assigned licensed lawyer co-signs each credential. No AI signs anything. What a co-signing lawyer signs, stakes and is exposed to is on the page for legal professionals.
· DecisionLex Arbitrage
Roadmap set: V0 VARA on testnet, V1 the LEXI Agent with MiCA and FIU-IND, V2 connectors and an API
The roadmap now has three versions. V0, on testnet: opinion issuance as an on-chain credential, VARA (Dubai) the base jurisdiction. V1, next up: a refreshed LEXI Agent built for long-horizon diligence, with persistent memory and iterative agentic search across many rulebooks, plus new jurisdictions starting with the EU (MiCA) and India (FIU-IND), so one opinion can span several. V2, after V1: 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.
The same three versions appear on the key facts page, with the maturity of each.
· On testnetLex Arbitrage
V0 runs end to end on Base Sepolia (testnet)
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. Credential id 0x8df7…7747 is a V0 test credential id, not a transaction hash.
The date is the founding team's confirmation of the end-to-end flow, not a chain event. The engine's first pass is work product, never the opinion. What a credential records, and the three-step check a relier runs, is on the credential page.
0x8df7…7747 · a V0 test credential id, not a transaction hash
firm id
lexi:firm:0x0000
subject
protocol:0x0000…0000
signatory
0x0000…0000 · licensed lawyer
opinion hash
0x0000…0000
Illustration of a V0 testnet record. Addresses publish once confirmed by the CTO.
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.
In progress
Hardening, then the audit.
Hardening
The V0 flow is being hardened before any mainnet deployment. Protocols, firms and signatories sign their own transactions in the client; an EU-hosted backend relays them and owns gas, nonces and retries. The field set on the credential page is the V0 target schema.
The audit
Contracts are audited before mainnet. No auditor is engaged yet. Mainnet follows the audit, not the other way round, and this log will carry the engagement as an entry when it happens.
Mainnet, post-audit
Targeted Q4 2026, VARA (Dubai) first. USDC price points publish at mainnet. Until then every credential on this site is a specimen or a testnet record, and there is nothing on mainnet to rely on.
What is next
Build state by version.
Build state labels describe build state, never traction
V0 · VARA (Dubai)On testnet· opinion issuance as an on-chain credential, end to end on Base Sepolia (testnet)
V1 · next upIn development· the refreshed LEXI Agent; the EU (MiCA) and India (FIU-IND); one opinion spanning several jurisdictions
V2 · after V1Planned· agent connectors (DocuSign, GitHub); the LEXI Verification Service API
US coveragePlanned· on the roadmap, no date
MainnetPlanned· targeted post-audit, Q4 2026, VARA first
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. The log gains an entry for each real milestone or decision, and a delay is recorded with its reason.
The trust layer for institutional Web3.
What is built and where it runs is on this page. What the credential records, and who built it, is one link away.