The checks, in order
Four checks on an opinion you hold.
A legal opinion handed over as a PDF shows a signature, a date, an addressee and a scope. It cannot show that the signer held a licence on that date or that you may rely on it. Unless it carries a digital signature you can validate, it cannot show that the file is the text signed either. Those checks run outside the file, with the register that issued the licence and with the signing firm. A LEXI credential records the signatory, the as-of date and hashes of the scope and the opinion on Base, and it names the parties that may rely, so most of the check takes one call. V0 runs on Base Sepolia testnet; nothing is live on mainnet.
The four checks below run in the order a relier meets them. Each says what to look for in the PDF and what to ask the firm, then what a LEXI credential records instead. Every source was read on 20 November 2026.
The checks, side by side
Where each check looks.
One row per check. The last column describes the V0 credential on Base Sepolia testnet, and no reliance attaches to any testnet credential.
| Check | What a PDF shows | What to ask the signing firm | What a LEXI credential records (V0, testnet) |
|---|---|---|---|
| Who signed | A signature over a lawyer's name, and the firm's letterhead. The file does not prove the licence; the register that issued it does. | Was this lawyer licensed on the opinion's date, and with which register? Then confirm the answer at that register. | The signatory and firm ID are public on-chain fields. The licence is still checked at the register: see Check who signed. |
| The text is the version signed | A scanned or typed signature proves nothing about the text; a valid digital signature shows whether the file changed after signing. | Did you issue this document, and does my copy match your file copy, page for page and annex for annex? | The opinion hash and the scope hash are committed on Base. Hash the file you hold and compare: a changed document stops matching. |
| Whom it is addressed to | The addressee line, and any clause naming other parties who may rely. | Is my entity the addressee, or a party you expressly authorised to rely? | The reliance mode is on-chain, and the credential lists who may rely: its named reliers. At mainnet, an on-chain reliance record shows that a relier accepted the terms, on a date. |
| Date and scope | The date of the opinion, its assumptions and qualifications, and the question it answers, in the body. | Which documents, and which versions, did the opinion cover? | The as-of date and expiry are on-chain, with a status of Live, Expired or Revoked. The scope text and the assumptions and reservations are public off-chain. |
Fig. 01 Four checks on a legal opinion a relier holds. The credential column follows the V0 schema on the credential page, as recorded on Base Sepolia testnet; no reliance attaches to any testnet credential. The exchange briefing splits the same ground into seven checks for a listing file, and the credential page reduces the on-chain part to three steps.
Check 1 · the signer
Check who signed.
The signature block names a lawyer and a firm. The licence behind the name is held by the bar or register that issued it, so that is where the check runs. Find the register through the regulator's own site, not through a link or a phone number printed in the opinion. Ask whether the lawyer was licensed on the opinion's date, not only on the day you search.
For a signatory registered with the Government of Dubai Legal Affairs Department, the Department keeps a directory of advocates and legal consultants (opens in a new tab); on it asked for a UAE PASS sign-in. The Department registers advocates and legal consultants on a roll it maintains. On request from the licensed firm, it issues a "To Whom it May Concern" certificate of licensing status for an advocate or a legal consultant.3 A relier can ask the signing firm to request one. For a signatory registered elsewhere, ask for the registration certificate and confirm it with the body that issued it.
Certificate authorities already follow a written version of this check. Before a certificate authority relies on a legal opinion for an Extended Validation certificate, the CA/Browser Forum's guidelines require it to verify the author's professional status by contacting the authority that registers or licenses the lawyer. To confirm the opinion is authentic, it calls or writes to the lawyer at the contact details listed with that authority and obtains confirmation from the lawyer's office. A digital signature that confirms both the document and the signer removes the need for that step.2 The order carries over to a relier: the register first, then the lawyer, reached through the register.
On a LEXI credential the signatory and the firm ID are public on-chain fields, and only a licensed lawyer co-signs. The credential does not record the licence itself, so the licence is still checked at the register that issued it.
Check 2 · the text
Check the text is the version signed.
A PDF can be changed after it is signed. Unless it carries a digital signature you can validate, nothing in the file shows whether it was. A valid digital signature still does not show the signer's licence; that check stays with the register. The conclusive check is against the signing firm's own copy.
Reach the firm through the contact details you found at the register. Ask it to confirm two things: that it issued the document, and that your copy matches its file copy in every page and annex, including the date and the addressee. Where the opinion names the documents it covers, such as a white paper version, check that the versions you hold are the ones it names.
A cryptographic hash makes the comparison exact. The firm hashes its copy, you hash yours, and if a single character differs, the hashes do not match. Hash the file exactly as the firm sent it, because a re-saved copy can differ in its bytes even when the words are the same.
On a LEXI credential the opinion hash and the scope hash are recorded on Base with the credential. Hash the opinion you hold and compare it with the opinion hash on the credential. The scope hash does the same for the document set the opinion covers, so a changed white paper or structure document stops matching too. That is the second step of the relier check on the credential page.
Check 3 · the addressee
Check whom it is addressed to.
Opinion practice limits who may rely on an opinion. In US practice, the Core Opinion Principles say a closing opinion may be relied on only by its addressee and by any other person expressly authorised to rely (section 4.2). The 2017 text was approved by the Joint Committee on Statement of Opinion Practices and the Legal Opinions Committee of the American Bar Association's Business Law Section, subject to approval by the Board of Directors of the Working Group on Legal Opinions Foundation.1
Read the addressee line first, then any clause that names other parties or lets them rely. Check that your entity appears under its legal name, not only under a brand or a group name. If it does not appear, the opinion still tells you what it says, but it does not show that you may rely on it. Take that question to the firm before the opinion goes into your file.
A LEXI credential names the parties that may rely on it, its named reliers, and its reliance mode is on-chain. At mainnet, an on-chain reliance record shows that a relier accepted the terms, on a date. Under Selective mode, a party that is not named may read the public metadata but cannot rely on the opinion and cannot open its body.
Check 4 · the date and scope
Check its date and scope.
A closing opinion speaks as of its date.Core Opinion Principles, section 4.1 (2017 text)
The same section says the opinion giver has no obligation to update a closing opinion for later events or legal developments, and section 1.7 says an opinion covers only the matters it specifically addresses.1 Read the as-of date with the assumptions and qualifications. Then read the question the opinion answers and what it leaves out.
Compare the date with what happened after it, in the project and in the rules. Dated regulator events on the corridor, each with what it does to an opinion's scope or date, are in the corridor tracker. What each named rule asks an opinion to state, with its read date, is in the legal opinion rules register.
On a LEXI credential the as-of date and the expiry are on-chain, with a status of Live, Expired or Revoked. Live means unexpired and unrevoked; it does not mean the opinion is a current legal conclusion. The scope text and the assumptions and reservations are public off-chain, and the scope hash binds the document set.
Red flags
Signs a document was changed.
None of these proves a forgery on its own. Each is a reason to stop and confirm with the firm before you rely.
- The copies differ. Your copy and the firm's file copy differ in a page, a date, the addressee or an annex.
- The hash does not match. A hash the firm gives you, or one on a record the firm controls, does not match the file you hold.
- The signature page stands alone. The signature sits on a separate page that names no document, or the page numbering breaks around it.
- The documents are not the ones named. The opinion names a white paper or a document set, and the versions you were given are different.
- The signer does not match the register. The name, the firm or the admission in the opinion is not what the register shows.
- The only route to the firm is the opinion itself. The opinion reached you only through the party it helps, and the only contact details for the firm are the ones printed on it.
- The firm will not confirm. Treat the opinion as unconfirmed until it does.
Under the Core Opinion Principles, a recipient ordinarily need not verify the opinions a closing opinion contains. It is not entitled to rely on one it knows to be incorrect, or where its reliance is otherwise unreasonable in the circumstances (section 1.4).1
On the credential
What a LEXI credential shows.
On a LEXI credential the text check and the addressee check move out of the PDF and onto Base, and the status shows whether the opinion has expired or been revoked. Each step of the relier check reads the on-chain record, in one call, and reading the public metadata is free. V0 runs on Base Sepolia testnet; nothing is live on mainnet.
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?
The three-step relier check in full, the field table and a specimen are on the credential page. What a listing team checks in an opinion it receives, item by item, is in the briefing on how exchanges verify an opinion. The relier page, for exchanges, VASPs and Licensed Distributors, maps a compliance file onto the credential.
What it does not show
- Whether the conclusion is right. The credential binds the text and names who co-signed it. The reasoning and the conclusion are in the opinion body, off-chain, for named reliers. An opinion expresses the lawyer's professional judgment and does not guarantee how a court will rule.1
- The licence. The signatory is a public field; the licence is checked at the register that issued it.
- Anything on mainnet. V0 credentials exist on Base Sepolia (testnet) only. No reliance attaches to any testnet credential.
Build state
Where LEXI stands 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.
Questions
Questions reliers ask about an opinion they hold.
How do I check that a legal opinion is genuine?
Run four checks in order. Confirm the signer's licence at the register that issued it, for the opinion's date. Confirm with the signing firm, through contact details you found yourself, that it issued the document and that your copy matches its file copy. Check that your entity is the addressee or a party expressly authorised to rely. Then read the as-of date and the scope. On a LEXI credential, the hash comparison and the named-relier check run against the on-chain record, as set out on the credential page.
Can I confirm a legal opinion with the firm that signed it?
Yes, and it is the conclusive check. Reach the firm through the contact details listed at the register, not the ones printed on the opinion. Ask whether it issued the document, on what date and to whom, and whether your copy matches its file copy. Certificate authorities follow the same order under the CA/Browser Forum's Extended Validation guidelines: they confirm a legal opinion with its author at the contact details listed with the licensing authority. If the firm will not confirm, treat the opinion as unconfirmed.
What are the signs that a legal opinion was altered?
Your copy differs from the firm's file copy in a page, a date, the addressee or an annex. A hash the firm gives you does not match the file you hold. The signature sits on a separate page that names no document. The documents the opinion says it covers are not the versions you were given. The firm can be reached only through details printed on the opinion, or will not confirm that it issued it. None of these proves a forgery on its own; each is a reason to confirm with the firm before you rely.
Does an on-chain record prove the opinion is correct?
No. It shows that the text has not changed since it was recorded, and who co-signed it. On a LEXI credential the opinion hash and the scope hash bind the text and the document set, and the signatory is a public field. Whether the conclusion is right is the lawyer's professional judgment, set out in the opinion body, and an opinion does not guarantee how a court will rule. V0 runs on Base Sepolia testnet, and no reliance attaches to any testnet credential.
Sources, read on 20 November 2026
- Core Opinion Principles, approved by the Joint Committee on Statement of Opinion Practices (28 March 2017) and the American Bar Association Business Law Section's Legal Opinions Committee (7 April 2017), subject to approval by the Board of Directors of the Working Group on Legal Opinions Foundation; the 2017 text as hosted by the South Carolina Bar. Sections 1.3, 1.4, 1.7, 4.1 and 4.2, read . scbar.org, PDF (opens in a new tab)
- CA/Browser Forum, Guidelines for the Issuance and Management of Extended Validation Certificates, version 2.0.4 (13 August 2026; listed as the current version, adopted by Ballot SC102), section 3.2.2.11.1, "Verified Legal Opinion" (pages 44 and 45), read . cabforum.org, EV Guidelines 2.0.4, PDF (opens in a new tab) · cabforum.org, documents page (opens in a new tab)
- Government of Dubai Legal Affairs Department: the directory of advocates and legal consultants, which, opened signed out on 2026-11-20, redirected to a UAE PASS sign-in page ("Login/Register", "Sign in with UAE PASS"); "Department Brief and History"; the Advocates Affairs and Legal Consultants Affairs service lists; and the two "To Whom it May Concern" certificate service descriptions, all read . lpsprd.legal.dubai.gov.ae (opens in a new tab) · Department brief (opens in a new tab) · Advocates Affairs (opens in a new tab) · Legal Consultants Affairs (opens in a new tab) · advocate certificate (opens in a new tab) · legal consultant certificate (opens in a new tab)
Every source above was opened at its URL on 20 November 2026. The Dubai directory was opened signed out; what a signed-in search shows was not checked. Law-firm summaries were not used as sources. Credential fields are described as the V0 schema on the credential page sets them out.
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)