Trade it where you issued it

Until now DALP issued, serviced, and settled regulated assets, and secondary trading happened somewhere else. The Trading Venue closes that gap. Each deployment runs its own permissioned orderbook, so the asset your compliance team configured is the asset your investors trade, under the same rules.

Trading Venue

An execution venue in front of your settlement layer

A market lists any two platform tokens as base and quote. Orders are EIP-712-signed intents the venue can neither fabricate nor alter, matching is deterministic with price-time priority, and matched fills settle on-chain in batches where one failing fill never blocks the rest. Each deployment runs its own book with its own liquidity; nothing is shared across customers.

Market structure

Central limit orderbook

Custody

Funds stay in trader wallets

Participation

Identity-registered only

Compliance

Token rules judge every fill

Your book, your rules, your evidence

For a bank or an asset manager, the hard part of secondary trading was never the matching. It was governance: every trade on outside infrastructure is investor activity you cannot see, gate, or evidence. The venue keeps that activity on the platform. Only participants in your deployment's identity registry can place orders, and the token's own transfer eligibility remains the final judge at fill time. The venue records signed orders, book events, fills, and matching skips into an audit trail from which its state is deterministically replayable.

1. 1
   Sign

   The trader signs an EIP-712 order intent with their own key. Settlement verifies the signature on-chain before any token moves.

2. 2
   Reserve

   The venue reserves the committed quantity in the trader's own wallet. The order joins the book only after the reservation confirms.

3. 3
   Match

   The engine matches by price-time priority, skips self-crosses, and bounds market orders with the price protection band.

4. 4
   Settle

   Fills settle in failure-isolated batches through each token's own compliance path, with fees taken atomically from the quote leg.

Non-custodial by construction

The venue holds no pooled funds, ever. An accepted order is backed by a reserved balance in the trader's own wallet: the tokens stay put, they just cannot be spent while the order works, and every partial fill releases exactly what it consumed. No omnibus account needs safeguarding, and no trading vault needs reconciling. The venue's contract also exposes no path to forced transfers, address freezes, or token recovery; the settlement path is unfreeze, then a transfer under the trader's own trading authorization.

Built for both sides of the house

Investors get a full trading screen in the Console: the order book ladder, depth chart, candles with volume, recent trades, an order ticket with a reserved-balance preview, working orders, and a trade blotter. Operators get a venue-operations surface: market listing, halt and resume, delisting behind a typed confirmation, per-market maker and taker fees, desk administration under maker-checker, and a venue health panel. Institutional desk funding follows four-eyes control: a proposer submits trading authorizations and desk limits, a distinct approver confirms them, and the book stays live because approval never touches individual fills.

Integrate in three calls

Everything the Console does rides the public v2 API, with generated TypeScript SDK operations to match.

Compatibility

No migration is required. The venue is an optional addon: the surface is additive v2 routes, new contracts deployed by their own factory, and new Console pages that appear only when a trading-venue addon is deployed. The /api/v1 surface and every existing v2 route stay unchanged. The broker or exchange legal role, fiat cash rails, and off-platform consent workflows remain with the operating institution.

Read the capability page → · Integrate with the API → · Operate the venue →