MERIDIANmrdn.trade Institutional access
00
Institutions · access & connectivity

Integrate in hours, not months.

Point your existing OMS/EMS at Meridian over the order-entry and market-data protocols every institutional desk already runs — the industry standard, so integration is hours, not months. No new tooling, no web3 learning curve.

01
Connect with the stack you already run

Institutional flow doesn't hit a matching engine directly — it arrives through an accountable broker. NYSE and NASDAQ have worked that way for decades. Meridian ports the pattern to Sui.

A wallet is not a session-based counterparty. A session assumes a provisioned, limit-bounded member firm — that's what the broker tier gives it to bind to.

Order entryMarket dataRESTRFQ
02
Isn't a broker tier just centralization? — three independent layers
Hardware

Matching integrity

Deterministic matching designed for TEE attestation — so validators can refuse to settle from an unattested engine.

Liability

Accountable access

Every order is broker-signed and strictly sequenced — who submitted what, in what order, and who is liable, is always attributable.

Public chain

Verifiability

Custody and a signed checkpoint live on Sui — anyone can audit the canonical state (how).

Each layer is bounded by hardware, by liability, or by the public chain — not by a promise.

03
How an order is authenticated
01

Broker-signed. Signed with the broker's registered key; verified against its on-chain public key.

02

Strictly sequenced. A per-broker sequence number (a nonce) — replay-proof, deterministic.

03

Bounded. Per-broker notional caps enforced at intake — exposure is always bounded.

04

KYC at the boundary. Identity and the regulated relationship live at the broker — like a member firm. The venue stays an infrastructure primitive.

04
The broker tier is live

Not a diagram — and already more than one.

More than one broker already runs on the venue — each a different product, each on the same unchanged engine and settlement. Two surfaces that share nothing but the rails beneath them.

Broker — AInstitutional execution
Broker — BEvent-contract market
Broker — nextYour seat
One venuedeterministic matching · Sui settlement
Different products · one unchanged engine
An institutional execution seat — a parent order worked into the market as timed child slices
Broker Atestnet · beta

An institutional execution seat

Parent orders worked into the market slice by slice, post-trade cost analysis, and more in beta. Account access sits behind a passkey — the surface won’t render your positions until a second factor clears. You keep custody the whole way: it signs and forwards, it never holds your funds.

A different market shape entirely — fully-collateralized event contracts that settle by a declared, published rule
Broker Btestnet

A different market shape entirely

Fully-collateralized contracts that mint as complete sets and settle by a rule declared and published up front. No leverage — solvency is an invariant of the contract, not a promise. A completely different product, on its own registered seat, over the same wire.

Two products that agree on nothing but the venue beneath them — the proof the tier generalizes. Independent third-party brokers — your own identity, stake and KYC, with the venue never seeing your flow — are the next tier.

05
Market data — tiered by cost, gated by design
Public

Cached snapshots

Ticker, top-of-book, recent trades — edge-cached REST that serves any number of pollers without touching the engine.

Real-time

Gated stream

Per-symbol order-book and trade streams for integrators and algo desks — every tick, behind provisioned access.

Colo

Dedicated feed

The engine's native binary feed, dedicated, for co-located traders — a later tier.

One principle underneath all three: public consumers never touch the matching engine. The engine publishes once; a separate distribution layer fans out.

06
Liquidity →Verify →

Connect your desk.

Building on Sui · testnet.