BEFORE YOU BEGIN
- Describe the legal entity and its actual role in the protocol.
- Separate company revenue, treasury holdings and client assets.
- Do not assume a DeFi label resolves the regulatory perimeter.
Start with the company’s role
“We build DeFi” leaves several unanswered questions. Does the company write software, operate an interface, control an upgrade key, charge transaction fees, provide a regulated service or invest its own treasury? Explain the activities separately. Identify who contracts with users and who receives the revenue.
A simple diagram should show the legal entity, protocol contracts, treasury wallets, conversion counterparties and bank account. Label the ownership or control at each point. Where control is shared, describe the arrangement rather than treating the word decentralised as a complete explanation.
Scope is a facts-based assessment
ESMA’s Q&A explains that crypto-asset services provided in a fully decentralised manner without an intermediary are outside MiCA’s scope, with decentralisation assessed case by case by competent authorities. The name of a project or its use of smart contracts does not settle that assessment.
Ask qualified counsel to map the actual services and control arrangements. Keep that analysis current when governance, fees or the interface changes. A legal analysis supports the account discussion; it does not require a bank to offer a particular product.
Make the revenue understandable
Prepare a sample reconciliation from a business event to the asset receipt, conversion and fiat credit. If revenue comes from protocol fees, explain the calculation and how the company is entitled to the proceeds. If it comes from development work, link the receipt to the contract and invoice.
Keep proprietary treasury activity visibly separate from any client assets or pass-through funds. Where multiple wallets belong to the company, maintain an approved wallet inventory with its purpose and control arrangement. The useful evidence is the commercial story plus the records that support it.
Answer the awkward questions before they arrive
The EBA’s risk-factor guidance includes factors relating to decentralised platforms, self-hosted addresses, customer behaviour and geography. An onboarding team may therefore need more than a product presentation. Prepare a concise explanation of the controls relevant to the business, including escalation ownership and how unusual receipts are investigated.
- Who can change the protocol or move treasury assets?
- Which revenue streams are expected, and from which markets?
- How are wallet activity and accounting records reconciled?
- What changes require a new regulatory or banking review?
Read the source in context. Provider policies, eligibility and national implementation can change. This field note explains an operating framework, not an account approval or individual legal opinion.
Back to all field notes