Liquidity locked before the deal.
A Middn vault is the proof layer behind every offer. Sellers fund USDC first, buyers reserve only what is available, and settlement moves through defined states instead of screenshots and promises.
Every offer starts with backing.
The vault is not a balance screenshot. It is the accounting surface that separates funds the seller can use, funds a buyer has reserved, and funds already released.
Available
Liquidity the seller can list, withdraw, or keep idle. No buyer can rely on it until it becomes reserved.
Reserved
When a buyer opens a deal, the matching amount is separated from available liquidity so another buyer cannot take the same funds.
Released
After payment is marked and confirmed, reserved USDC releases to the buyer or moves into dispute/refund flow.
Available → reserved → settled.
The product can feel simple because the vault state is explicit. Each action changes what the funds are allowed to do next.
Fund
The seller sends USDC to their vault address.
List
Only available funds can back a public or private offer.
Reserve
The buyer opens a deal and the matching amount locks.
Confirm
Payment is marked, reviewed, then released or disputed.
Settle
Reserved USDC releases to the buyer, or returns by rule.
What buyers verify.
- The offer is backed by enough reserved USDC.
- The seller cannot reuse the same funds in another active deal.
- The release path is tied to the current deal state.
What sellers control.
- How much liquidity is listed, reserved, or withdrawn.
- Which payment rails, limits, and buyer requirements are accepted.
- When a paid deal is ready to release or needs escalation.
The vault makes the promise measurable.
In private beta, Middn keeps limits conservative while the production contract path, relayer, and audit reports are prepared. The goal is simple: make the important states visible before users rely on them.