A trust layer for direct trade.
Middn is an AI-assisted, privacy-first, smart-contract powered P2P trading layer. This draft explains the product thesis, escrow flow, AI guidance, privacy direction, market design, and proposed MID token economics.
The thesis
The internet made it easy for two strangers to find each other. It did not make it easy for them to safely exchange value without handing custody to a centralized platform. Middn exists for that missing middle layer.
The product vision is simple: users keep wallet control, the smart contract holds escrow state, the AI agent explains what is happening, and privacy proofs reduce how much personal data needs to be exposed.
Middn is not presented as a guarantee of safety, profit, or legal protection. It is product infrastructure designed to make trade state, evidence, and release decisions clearer.
Why the old way breaks
P2P trading often forces users into two bad options: give funds to a centralized exchange, or coordinate privately across chats, screenshots, wallets, bank apps, and trust signals that are hard to verify.
What Middn is designed to reduce
- Custody risk from platforms that hold assets as part of the trade experience.
- Off-platform confusion where critical proof lives in Telegram, WhatsApp, email, or screenshots.
- Blind trust in unverifiable counterparties, fake reputations, or unclear payment instructions.
- Dispute chaos when neither side has a clean timeline of what happened.
The protected trade flow
The core product flow is deliberately simple. A user should be able to connect a wallet, open a room, agree terms, fund escrow, submit proof, and release or dispute without needing to understand smart contracts.
Room states
| State | What happens | User sees |
|---|---|---|
| draft | Buyer and seller review amount, asset, payment method, and requirements. | Chat, terms, risk hints, countdown to accept. |
| accepted | Both sides approve the room before funds move. | Escrow can be generated. |
| funded | The crypto side deposits into the smart contract. | Contract address, lock state, timer. |
| proof | The payment side uploads evidence and follows instructions. | AI proof check and seller confirmation. |
| release | Seller confirms payment or dispute review resolves the room. | Release, refund, or dispute outcome. |
Smart contract escrow
Middn's escrow direction is non-custodial: the application coordinates the room, but the contract holds the funded asset and exposes clear state transitions. Middn should not be the account that receives user funds.
Simplified contract state
Design principles
- Explicit funding before any payment instruction is shown.
- Terms hash so the room can prove which conditions were accepted.
- Timeouts so inactive rooms do not trap attention forever.
- Dispute branch where evidence is organized before any human review.
The AI trade agent
The AI agent is not a black-box judge and should not sign transactions for the user. Its role is to make the room easier to understand: explain steps, detect risk, compare proof against terms, and prepare neutral evidence summaries if a dispute appears.
Agent tasks
- Explain each stage in plain language before the user clicks.
- Warn when someone tries to move the trade to WhatsApp, Telegram, or email.
- Check payment proof for amount, date, sender name, reference, and method.
- Summarize dispute evidence without deciding the outcome alone.
Privacy and ZK direction
Middn should not force every user into maximum disclosure. Some trades may need stronger verification, but the product direction is selective disclosure: prove only the attribute needed for that room.
| Signal | Can prove | Should avoid exposing |
|---|---|---|
| wallet | User controls the wallet address. | Private key, seed phrase. |
| reputation | Level, success rate, completed trade count. | Full trade history. |
| identity | Verified person or business status when required. | Full documents to every seller. |
| jurisdiction | Eligible or blocked status for a market rule. | Unneeded personal address data. |
KYC and ZK are not automatically contradictory. The goal is not to remove all verification, but to avoid repeatedly exposing raw identity data when a reusable proof can express the needed trust signal.
Markets on Middn
The same escrow room model can support different markets. Each market changes the proof requirements, payment rules, and room language, but the user should always understand: who sends what, who receives what, what is locked, and what happens next.
Market-specific rules
| Market | Primary need | Middn layer |
|---|---|---|
| P2P | Payment proof, deadlines, seller requirements. | Escrow room + AI proof check. |
| OTC | Negotiated terms, large tickets, private access. | Pre-escrow agreement + staged approvals. |
| RWA | Documents, invoices, milestones. | Milestone escrow + evidence bundles. |
| NFT | Metadata, wallet ownership, collection checks. | NFT escrow + AI metadata warnings. |
| Digital | Delivery proof, revisions, service milestones. | Freelance-style escrow room. |
MID tokenomics draft
MID is planned as the coordination asset for incentives, reputation, fee design, and future governance. The numbers below are a draft allocation framework and should be treated as product planning, not an investment guarantee.
The public sale concept currently uses 0.50 USD per MID in the local testnet prototype. Final sale mechanics, compliance requirements, and chain deployment would need to be confirmed before any real launch.
Roadmap and open work
The next phase is about turning the prototype into a coherent beta: fewer screens, clearer room states, stronger wallet connection, testnet escrow contracts, and a focused onboarding story for beta testers.
| Phase | Focus | Status |
|---|---|---|
| 01 | Public landing, docs, whitepaper, app prototype visual system. | in progress |
| 02 | P2P deal room, pre-escrow agreement, chat, timers, seller requirements. | prototype |
| 03 | Testnet contracts, fake USDC, buyer/seller state simulation. | planned |
| 04 | AI proof reading, dispute summaries, scam warnings. | planned |
| 05 | Privacy proof layer and reusable reputation signals. | research |
Complete Middn Whitepaper
Download the full standalone whitepaper package.
Important: this whitepaper is a product draft. It does not make financial, legal, security, or performance guarantees. Contract code, audits, token terms, and compliance flows must be finalized before any real-money deployment.