u/Artistic_Quit2878

Genuine question I've been thinking about.

Smart contracts are self-executing — once deployed on a blockchain, they run automatically based on coded conditions with no human intervention possible. That's the whole point. But what happens when the code has a bug that causes unintended execution, and someone loses significant money as a result?

A few scenarios I'm curious about from a legal standpoint:

The developer wrote the code in good faith but made an error. The user read the contract terms and agreed to them. The bug triggers, and funds are lost. Is the developer liable?.

And what jurisdiction even applies? The developer might be in Germany, the user in Brazil, the blockchain nodes distributed globally, and the loss denominated in a token issued by a foundation in the Cayman Islands.

Curious whether anyone with a legal background has seen cases like this or has a view on how existing contract law frameworks apply to code that executes without any human in the loop.

I've been following the rollout and have a genuine question for anyone with a legal background.

The idea behind MiCA was to create a safe, regulated crypto environment across the EU. But in practice, the licences are mostly concentrated in a handful of countries — Germany, Netherlands, France, Malta, Cyprus — the same places that have always dominated European finance.

If you live in a country where no local regulator has issued any MiCA licences yet, what does that actually mean for you as a user? Are you better protected than before, or do you just end up using offshore platforms anyway — which are completely outside MiCA's reach?

Curious whether MiCA is genuinely helping everyday crypto users or mostly just adding compliance costs for businesses while leaving a lot of people in the same position they were before.

Noticed two new additions to the ESMA CASP register in the last days of April 2026. Estonia and Croatia have each issued their first MiCA licence, bringing the total number of EU jurisdictions actively issuing CASP authorisations to 22.

A couple of things worth noting about the Estonia entry specifically. The licence was actually approved back on 17 November 2025, but only appeared in the ESMA register on 5 December 2025. Croatia's licence was issued in April 2026 and appeared shortly after. So the register isn't always real-time, and there's likely a lag between national regulator approval and ESMA publication that varies by country.

Both companies declare cross-border intent across 30 EU/EEA markets, which is the whole point of the MiCA passporting framework.

Overall register snapshot as of late April 2026:

• 191 total CASP licences recorded
• 22 jurisdictions now issuing licences
• Germany, the Netherlands, France, Cyprus, and Malta account for roughly 60% of all licences

The concentration in those five is worth flagging. MiCA was supposed to create a level playing field across the EU, but in practice, licensing is highly centralised. Smaller member states are joining slowly and often with just one or two licences initially. Estonia's joining is interesting given its history as a crypto-friendly jurisdiction, though the single licence so far suggests the new MiCA framework is more demanding than the old VASP registration many companies used previously.

Source: ESMA CASP register — esma.europa.eu/esmas-activities/digital-finance-and-innovation/markets-crypto-assets-regulation-mica

So a Delta Air Lines employee named Lattice Jones decided to sue her employer for discrimination — race, religion, and disability, including long COVID. She'd worked there for 12 years, had what sounds like a genuine grievance, and then made one very avoidable decision. She represented herself and used ChatGPT as her legal consultant.

It did not go well.

During her deposition, she was visibly reading answers from her screen. When questioned about it, she admitted ChatGPT was open on her laptop — then refused to answer whether she was actually feeding questions into it. She also argued the conversation was protected by the attorney-client privilege. The judge disagreed on the grounds that a chatbot is not a licensed attorney. Hard to argue with that logic.

On top of that, she'd been secretly recording the proceedings without court permission, which is its own violation. And despite getting not one but two deadline extensions, she still couldn't produce the evidence needed to support her claims.

The case was dismissed with prejudice. That means she can't refile against Delta on the same grounds. Ever.

The frustrating part is that this didn't have to happen. The underlying claims — discrimination, harassment, failure to accommodate — might have had merit. But procedural failures, evidentiary gaps, and using an AI tool in ways a court simply won't accept turned a potentially legitimate case into a permanent loss.

AI is genuinely useful for understanding legal concepts, drafting documents, or researching general information. But it doesn't know your specific jurisdiction, it can't be held accountable, it won't object when opposing counsel does something improper, and it definitely doesn't count as legal representation in a federal court.

Source: cybernews.com/ai-news/delta-airlines-lawsuit-chatgpt and jdsupra.com/legalnews/deponent-s-use-of-a-i-to-answer-7503271