Fast matching off‑chain. Settlement on‑chain.
DPM splits the work. Plaee’s off‑chain order book matches orders instantly, and Polygon smart contracts settle every trade where anyone can verify it. Keys are kept in a hardware enclave, and you control them.
Four boundaries
Plaee
Platform engine
The trading UI, embedded as an iFrame in your app, and the off‑chain order book.
Operator premises
DPM Wallet App
Lightweight middleware on your infrastructure. It handles treasury policy, balance validation and signing requests. Used in Shared Balance.
Turnkey TEE
Key enclave
A hardware‑isolated enclave holds the private keys and signs transactions without exposing them.
Polygon
Settlement
Proxy contracts hold user positions and operator funds. They only act on a valid signature from the matching key.
Every operator, one order book.
Every operator on DPM trades on the same exchange, whatever their model. An order placed in your app can match against users from every other DPM operator. You get tighter prices and fuller markets than your user base would produce on its own.
Operator A
Shared
Operator B
Segregated
Operator C
Standalone
DPM exchange
One order book, one pool of liquidity
A wallet per user, in milliseconds
On a user’s first visit, DPM sets up a dedicated proxy contract for them on Polygon. The user does nothing.
1
User opens the prediction tab
Inside your platform.
2
Plaee requests a new customer
The Sign‑Up module detects a first‑time user and asks your DPM Wallet App.
3
Address created in Turnkey
The DPM Wallet App has Turnkey TEE generate a new address.
4
Address returned to Plaee
The DPM Wallet App forwards it to the Sign‑Up module.
5
Proxy deployed on Polygon
Plaee deploys the user’s proxy contract, and the user can start trading.
Plaee matches. You approve.
An order can only reach the order book or the blockchain after your infrastructure has approved and signed it.
Trade flow for the Shared Balance model
1
Open order
The user clicks Buy.
2
Balance check & debit
Your backend checks the internal ledger and debits the amount.
3
Routing
Plaee sends the order to your DPM Wallet App.
4
Signing
The DPM Wallet App has Turnkey TEE sign the order.
5
Order book
The signed order goes straight into the live order book.
6
Match
Once it matches, Plaee broadcasts the trade to Polygon.
7
On‑chain execution
The trade contract pulls USDC from your Operations Wallet and mints outcome tokens to the user’s proxy.
8
Redeem
The user redeems winning tokens. The payout goes to your Operations Wallet, and you credit the user’s balance.
Three habits that keep it safe
Managing funds in the Segregated model
Operation wallet
Keep it lean
Hold only enough USDC there for expected transfers. Top it up from Master when it falls below a low‑water mark, and sweep the excess back above a high‑water mark.
Keys
Isolate the keys
Never keep the Admin key (Master) and the Operation key in the same environment. Moving funds out of Master should require separate sign‑off from your finance or security team.
Ledger
Reconcile daily
Plaee pays the gas, so you only track USDC. If the totals don’t match, pause Operation wallet distributions.
Daily reconciliation
Master USDC + Operation USDC + Σ User wallet USDC = Total expected platform liability