Twitxy Saved

Ben Dhaya | Infinilex

@benInfinilex

Web3 Growth & Partnerships
President of Growth @Infinilex
Cross-border ecosystems | Launch readiness | Global expansion
france Joined May 2026
50 Following 21 Followers 58 Posts

Latest posts 5

Ben Dhaya | Infinilex @benInfinilex
Regulations change. But how do you know if the legal opinion you're relying on is still valid?

With major compliance milestones approaching across the UAE, EU and US, static legal documents aren't enough.

This is exactly why we're building @LEXIProtocol.
LEXI Protocol Verified account @LEXIProtocol 2d
Three deadlines on the corridor fall in January.

1 January 2027, UAE: Article 83 of Federal Decree-Law 33 of 2025 gives firms in scope one year from 1 January 2026 to adjust their status under the federal Capital Market Authority. The law allows that period to be extended.

About 8 January 2027, EU: three months after ESMA's opinion of 8 October, by which national supervisors should require crypto-asset service providers to clear their remaining exposure to asset-referenced and e-money tokens that don't comply with MiCA.

18 January 2027, US: the latest date the GENIUS Act can take effect. Section 20 sets the earlier of that date or 120 days after the final implementing regulations.

If your file holds a legal opinion or a compliance memo on any of these, check which side of the deadline it was written on.

General information, not legal advice.
View quoted post on X
Ben Dhaya | Infinilex @benInfinilex
Before relying on a legal opinion, check its status, document hashes and whether you’re a named relier.

@LEXIProtocol makes these checks verifiable onchain. Live doesn’t mean the law hasn’t changed.

x.com/LEXIProtocol/s…
LEXI Protocol Verified account @LEXIProtocol Nov 2
How a relier reads a LEXI credential, in three steps. Each step reads one field on Base.
1. Status: Is it Live, or Expired or Revoked? The as-of date, the expiry and any revocation are on-chain.
2. Hashes: Hash the PDF and the scope text you hold and compare them with the two commitments on the credential. One changed character and they don't match.
3. Reliance: Is your entity on the named-relier list, and is there a reliance record showing you accepted the terms?
Live means unexpired and unrevoked. Whether the opinion still fits the law is a separate question, answered by its as-of date and what regulators did after it.

Reading the public metadata is free. V0 runs on Base Sepolia testnet, and no reliance attaches to any testnet credential.
General information, not legal advice.
View quoted post on X
Ben Dhaya | Infinilex @benInfinilex
Launching a token in Dubai?

Your issuer’s licence status is only half the story. Who distributes it and what they must check could change your launch plan.

Our breakdown 👇
x.com/LEXIProtocol/s…
LEXI Protocol Verified account @LEXIProtocol Oct 22
VARA teardown #1: issuing a token from Dubai without a VARA licence.

VARA's Virtual Asset Issuance Rulebook sorts issuances into three groups. Category 1 covers fiat-referenced and asset-referenced virtual assets and needs a VARA licence. Exempt VAs, such as non-transferable tokens, have no requirements before issuance. Everything else is Category 2.
Category 2 needs no VARA licence. The condition is in Rule I.E.1: "Entities in the Emirate may only issue Virtual Assets that fall within Category 2 above provided that, all placement and distribution is carried out by a Licensed Distributor." A Licensed Distributor is a firm VARA has licensed for Broker-Dealer Services.

That puts the work on the distributor. Under Part IV of the Broker-Dealer Services Rulebook, it must:
1. Carry out "comprehensive due diligence" on the token and on the issuer.
2. Send VARA the whitepaper, the risk disclosure statement, its due diligence reports and a signed declaration.
3. Wait out a submission period of 15 working days before anything is placed.
4. Keep that due diligence current for as long as it distributes the token, and suspend at once if it has reason to suspect the token no longer complies.

Two points founders often miss: The 15 working days passing without comment gives no approval: Rule IV.D.7 says VARA is not deemed to have approved the asset. And a material change to the token or the issuer sends the distributor back to redo its due diligence.

So the useful question for an issuer is what its distributor needs on file before it signs that declaration. Ask before the whitepaper is final.

Rulebooks dated 19 May 2025. "The Emirate" is Dubai outside the DIFC. General information, not legal advice. LEXI is not a law firm and is not licensed by VARA or any financial regulator.
View quoted post on X
Ben Dhaya | Infinilex @benInfinilex
Your product changed does your legal opinion still cover it?

See what we’re building at @LEXIProtocol: x.com/LEXIProtocol/s…

#Web3 #LegalTech
LEXI Protocol Verified account @LEXIProtocol Sep 25
We built LEXI to settle one question: does this protocol need a licence in this jurisdiction, and can a counterparty rely on the answer?

Here is V0 running end to end on Base Sepolia. Documentation in, engine first pass, opinion issued, credential minted, and the relier accepts on chain.

The engine says what it cannot answer without more facts, and splits that into what the client has to confirm and what counsel has to obtain and read for themselves. It drafts with citations to the VARA rulebooks, checks its own citations against the corpus, and lists the ones it rejected instead of fixing them quietly.

The credential is dated, scope bound and non-transferable, and it names who may rely on it. The opinion body stays off chain and encrypted. Accepting reliance is its own on-chain transaction, signed and paid for by the relier.

Worked example on public documentation, not a client engagement. V0 is on testnet. Mainnet comes after hardening and the audit.
View quoted post on X
Ben Dhaya | Infinilex @benInfinilex
What does onchain verification prove?

A verified wallet alone doesn’t establish a project’s legal position.

LEXI is building records of lawyer-signed opinions with clear scope, jurisdiction and dates.

x.com/LEXIProtocol/s…
LEXI Protocol Verified account @LEXIProtocol Oct 19
@coinbase Verifications on @base attest that a wallet belongs to a verified Coinbase account. The project's README sets the limit: the attestation "should not be relied upon by you or any third party" for any legal, compliance or contractual purpose.
An identity attestation settles whose wallet it is. A counterparty in Dubai also needs to know whether the holder's activity is lawful there, and who carries the liability if that answer turns out wrong.
A legal opinion answers those two. Its reliance clause names who may act on the answer and for what purpose, and the opinion speaks as of a stated date. The same README makes the point about dates for its own product: an attestation reflects account status at the time it was issued.
We designed LEXI to put those facts on chain and keep the opinion body off it, so a counterparty can check who may rely on the opinion and what date it speaks from before it acts.
Not legal advice.
Source: github.com/coinbase/verif…
View quoted post on X