regulatory strategy

Built for trust. Designed for scrutiny.

Middn is privacy-first, non-custodial escrow infrastructure built with compliance in mind. We don't hold your funds, we don't impersonate a bank, and we don't pretend regulation doesn't exist. Here is exactly how we think about it.

Non-custodial escrow Audit-ready contracts Neutral dispute panel MiCA-aware roadmap

A note on scope. Middn is a technology protocol, not a bank, broker, or licensed payment institution. We make no claim to hold licenses we have not obtained, and nothing on this page is legal advice or a guarantee of any regulatory outcome. Our goal is to describe our architecture and intentions transparently as we prepare for institutional-grade adoption.

Why regulation matters

01 — principles

Trust is the product

Peer-to-peer value transfer only works if both sides believe the rules will be enforced fairly. Regulation, done right, is not friction — it is the shared rulebook that lets strangers transact at scale.

We treat compliance as a feature that protects users, not a box-ticking exercise bolted on at the end.

Regulation is arriving anyway

Frameworks like the EU's MiCA, the Travel Rule, and national VASP regimes are reshaping how crypto-adjacent services operate. Building as if they don't exist is a liability for users and investors alike.

We would rather architect for the rules early than retrofit under pressure.

How Middn differs from centralized exchanges

02 — positioning

DimensionCentralized exchangeMiddn

Custody of funds Holds user balances in pooled wallets Funds locked in on-chain escrow, never pooled

Counterparty You trade against the exchange You trade peer-to-peer with real people

Rules of a trade Set globally by the platform Set by each seller, shown before you commit

Failure mode Platform insolvency risks all balances Escrow contract releases only on agreed conditions

Transparency Internal ledgers, rarely public On-chain, verifiable reserves & settlements

The non-custodial escrow model

03 — how funds move

Seller locks

The seller deposits USDC into the audit-ready escrow contract. Middn never takes possession.

on-chain

Buyer reserves

The buyer reserves a portion. The contract earmarks it and starts a payment window.

on-chain

Fiat off-chain

Buyer pays the seller directly via the agreed method. Middn does not touch fiat.

peer-to-peer

Confirm

Seller confirms receipt — or the buyer's proof + timer triggers review.

on-chain

Release

The contract releases USDC to the buyer's wallet. Settlement is final and visible.

on-chain

Seller-controlled requirements

04 — flexible by design

KYC is a seller choice, surfaced upfront

Middn does not impose a single global identity policy. Each seller declares the requirements for their offers — verified ID, no-VPN, region limits, minimum history — and those terms are shown to the buyer before they commit.

A seller who wants KYC can require it; a buyer who wants a KYC counterparty can filter for it. The protocol enforces the terms both sides agreed to.

Conditions travel with the deal

Restrictions aren't decorative — they're attached to the reservation. KYC, VPN, and regional rules become part of the dispute record, so resolution is judged against terms that were transparent from the start.

This keeps responsibility where it belongs and gives reviewers an objective basis for decisions.

Privacy & compliance

05 — not a trade-off

What we protect

You keep custody of your own funds and keys.
No pooling, no rehypothecation, no hidden ledger.
Minimal data collection — we don't ask for what we don't need.

balanced

What we enable

Sellers can require verification when their risk demands it.
On-chain settlement leaves an auditable trail where it counts.
Architecture ready to support Travel-Rule data where legally required.

Privacy and compliance are often framed as opposites. We design for both: protect the ordinary user's data by default, while giving sellers and future regulated partners the tools to meet their obligations when the law requires it.

Risk engine & fraud prevention

06 — every trade scored

Signals weighed per reservation

Counterparty historystrong

Completion rate99.4%

Payment-method riskmoderate

Velocity / anomalylow

Device & session trustverified

81trust score

Cleared · auto-approved with standard escrow window

Each reservation is scored in real time from on-chain reputation, behavioural signals, and the seller's own conditions. High-risk patterns extend the escrow window, prompt additional checks, or route to manual review — before funds can move.

Dispute resolution framework

07 — neutral by construction

Buyer evidence

Payment proof, timestamps, and reference are submitted to the case record.

key 1

Seller evidence

Account statements and the offer's declared conditions form the other side.

key 2

Neutral mediators

Independent reviewers assess the record against agreed terms. Release needs 2 of 3 keys.

2-of-3 quorum

No single party — including Middn — can unilaterally move disputed funds. Resolution runs in a shared case chat with the mediator and the counterparty, judged against the conditions both sides accepted, and finalised by a 2-of-3 multi-signature decision.

MiCA & licensing roadmap

08 — preparing in public

2025 · foundation

Non-custodial architecture & auditsdone

Escrow contracts independently audited; reserves verifiable on-chain. The protocol is designed so Middn never takes custody — the cleanest starting point for any future regime.

2026 · engagement

Legal mapping & advisor onboardingin progress

Working with specialist counsel to map Middn's model against MiCA, national VASP regimes, and the Travel Rule — identifying which activities are in scope and where partnerships or registrations may be required.

2026–27 · alignment

Travel-Rule readiness & partner integrationsplanned

Building optional data-exchange rails so regulated partners and sellers can meet obligations where required, without imposing surveillance on every ordinary user.

future · licensing

Jurisdiction-specific registrationsexploratory

Where the law requires it for specific features or markets, we intend to pursue the appropriate registrations or licensed partners. We will only ever claim status we have actually obtained.

Regulatory-first architecture

09 — compliance in the design

Settlement

On-chain escrow

Audited, non-custodial contracts hold funds; every release is a public, verifiable event.

Identity

Seller-defined verification

KYC and restrictions are policy at the offer level, enforced by the protocol and recorded with the deal.

Risk

Real-time scoring engine

Behavioural and reputation signals gate each reservation before funds can move.

Governance

2-of-3 dispute keys

Neutral, multi-party resolution — no single actor controls disputed funds.

Data

Minimise & segment

Collect only what's needed; design for Travel-Rule data exchange where the law requires it.

Frequently asked questions

10 — straight answers

No. Middn is a non-custodial technology protocol, not a bank, broker, or licensed payment institution. We never claim licenses we do not hold. Where specific features require registration or a licensed partner, we intend to pursue that explicitly.

No. Funds sit in audit-ready on-chain escrow contracts and are released only when the agreed conditions are met. Fiat is paid peer-to-peer between users — Middn never touches it.

It depends on the seller. Each seller sets their own requirements, shown before you commit. Some require verified ID; others don't. You can filter for the counterparty conditions you're comfortable with.

Through a neutral panel using a 2-of-3 multi-signature process, judged against the conditions both parties accepted. No single party — including Middn — can move disputed funds alone.

We are actively mapping our model against MiCA and related regimes with specialist counsel, and architecting for Travel-Rule readiness. We make no promise about specific regulatory outcomes — only a commitment to engage early and transparently.

Compliance-minded by design.

We'd rather over-communicate our approach than hide behind legalese. Read the protocol, inspect the contracts, or talk to the team.

Read the protocol → Security & audits