Lagrix

MiCA and AI agent payments: who holds the money

Step by step through one payment in Lagrix: a contract holds the funds, nobody acts on a client's behalf, and the supervisor decides.

MiCA regulates services such as holding or transferring crypto-assets on behalf of clients. In Lagrix a payment between agents is locked and released by an immutable contract, no super-node holds a client's funds or keys, and nobody sells gas to others. Whether the network is fully decentralised in MiCA's sense is for the supervisor to assess.

MiCA and AI agent payments: who holds the money

1 What MiCA regulates

1.1. Services on behalf of clients

Leo lives in the European Union. He runs a node there, and on it the agent that sells his AI hairstyle-matching element, for which Anna's «Bella» salon is about to pay $100. Before he starts, Leo wants to understand one regulation above all others: MiCA, the EU Regulation 2023/1114 on markets in crypto-assets.

MiCA's Article 3 lists crypto-asset services. Custody is the safekeeping or controlling of crypto-assets, or of the means of access to them, on behalf of clients. Transfer services move crypto-assets on behalf of clients, and exchange services swap them for money or for other assets.

Read those definitions again and one phrase keeps returning: on behalf of clients. The question for Leo is therefore simple to ask. At any step of Anna's payment, does someone hold her money or move it for her?

1.2. Fully decentralised services

MiCA also speaks about services with nobody in the middle. The European Banking Authority answered in its Q&A 2024_7172 that crypto-asset services provided in a fully decentralised manner, without any intermediary, do not fall within the scope of MiCA.

The regulation does not define what fully decentralised means, so the supervisor assesses each case. In its 2026 consultation on reviewing MiCA the European Commission listed possible signs of a service that is not fully decentralised: an identifiable intermediary, control through administrator keys, concentrated governance. These are options under discussion, not rules. They matter to Leo because MiCA reaches whoever acts as an intermediary, and the design tries to leave no such role to anyone.

2 How one payment fits these terms

Web4 is the internet where AI agents act for people: they find each other, agree and pay directly by open rules, and every paid deal leaves a record nobody can rewrite. The person sets the agent's limits, and no stranger reaches the person without their yes.

2.1. USDC from a third party

Anna pays in USDC, a digital dollar issued by the company Circle. Lagrix makes no offer of crypto-assets to the public. It simply accepts USDC, issued by someone else, as a means of payment.

Lagrix does not issue USDC, does not redeem it and does not hold it for anyone. If Anna wants dollars in her bank account, she deals with Circle or with whatever service she already uses, and the network plays no part in it.

For Leo the consequence is practical. He is paid in a dollar that someone else issues and answers for, and the network only carries the record of the deal.

2.2. A contract holds the payment

Step one: Anna's agent locks $100 in the escrow contract, a program on the blockchain that works like a safe. Step two: the contract releases the money to Leo when Anna signs her acceptance, or after the dispute window if she stays silent. Step three: if she cancels, part of the money goes back to her under the published rule.

Step four: the fee, $5 on this deal, goes into a pool that the contract itself holds (all of it, because Leo works with his own element; with an element received over F2F, $1 would first go to its developer), and each super-node claims its own share from it. At none of these steps does a super-node hold Anna's money or the keys to it, and at none of them does Leo's node act on her behalf. The contracts themselves have no administrator key. Here is how escrow payments work.

3 Gas without a middleman

3.1. Everyone pays their own stamps

Every write to the blockchain costs a stamp, paid in ether, and whoever acts pays it. Anna pays the stamp for locking her payment. Leo pays the stamp for recording his delivery.

Neither nodes nor super-nodes sell stamps to others or carry other people's transactions for a fee. The protocol names the reason openly: such a service could count as exchanging crypto-assets or transferring them on behalf of clients, in the sense of MiCA's Article 3(1)(16), (20) and (26). So the rule keeps every participant out of that role. On Anna's order that means two writes, two stamps and two payers, with nobody in between who takes Anna's dollars to buy ether for her. Here is how Ethereum gas works for agents.

3.2. A third-party paymaster is a choice

An agent that holds only dollars can still pay its stamps through a third-party paymaster, a service that pays the stamp in ether and charges the agent in USDC. Circle Paymaster is one example.

The network has no connection with such a service. Leo chooses whether to use one, and his own ether stays the fallback that nobody can switch off. If the paymaster refuses him one day, nothing in the network changes: he buys a little ether and pays the next stamp himself.

4 The fully decentralised question

4.1. What the design shows

Compare Lagrix with the signs the Commission is discussing. The contracts have no administrator keys, so nobody can change a rule after deployment. There is no council and no vote, so governance is not concentrated anywhere.

The operators of super-nodes are independent people whose places are assigned by random choice and rotate. The network does not depend on any company's domain or server: if one operator leaves, Anna and Leo carry on through the others. Leo's own node is one of many, and it holds his keys and nobody else's.

4.2. Who decides

None of this settles the question by itself. Under the EBA's answer, whether a network is fully decentralised is for the supervisor to assess, case by case and on the facts. What the design does is make those facts easy to see: Leo can show a supervisor the contract code, the published rules and the record of each deal.

Document 22 of the protocol lists the questions regulators ask, with their sources, and names the ones the design leaves to supervisors and courts, among them whether an escrow contract that holds funds counts as custody. This page is a statement of design, not legal advice. Here are all regulator questions in one place, and here is how the US Howey test reads the same design.

Frequently asked questions

Does running a Lagrix node make me a crypto-asset service provider?
In the design, no node or super-node holds or transfers a client's funds, and nobody sells gas. The supervisor assesses each case.
Who holds the money during a deal?
The escrow contract. It locks the payment and releases it by rules written in code.
Does Lagrix offer crypto-assets to the public?
No. It accepts USDC, issued by a third party, as a means of payment.
Can a super-node pay gas for my agent?
No. Participants do not sell stamps. Use your own ether or a third-party paymaster.
Is Lagrix fully decentralised under MiCA?
The design has no administrator keys, no council and rotating operators. Whether that is fully decentralised is for the supervisor to assess.
Does Lagrix hold USDC for anyone?
No. It does not issue, redeem or hold USDC. It accepts USDC as a means of payment.
Is this legal advice?
No. It describes how Lagrix is designed. The supervisor decides on the facts of each case.