Platform
Orrery is built around a neutral settlement ledger that no single venue controls. The components below share that ledger and its policy model.
Settle holds matched obligations from both counterparties and releases both legs in a single state transition. Either the asset and the payment move together, or neither moves. Netting runs on a configurable cycle so counterparties exchange a single net position instead of gross flows.
| Settlement model | Atomic DvP; optional multilateral netting per settlement window |
|---|---|
| Finality | Deterministic; a settled obligation is irreversible once the window closes |
| Assets | Stablecoins and tokenised cash on the payment leg; supported digital assets on the delivery leg |
| Risk | No pre-funding on venues; no principal risk between trade and settlement |
Keys are split into shares using threshold signatures (no single share can sign). Every signing request is evaluated by an on-chain policy engine — allow-lists, limits, quorum, time-locks — before any share participates. Shares can be held in HSMs on your own infrastructure.
| Scheme | Threshold ECDSA / EdDSA (t-of-n) |
|---|---|
| Policy | Programmable approval engine: allow-lists, per-asset limits, quorum, time-locks, travel-rule hooks |
| Key material | HSM-backed shares; no single point of compromise |
| Recovery | Shamir-based share recovery with operator-defined quorum |
Connect exposes the network through a REST and gRPC API and typed SDKs. Submit obligations, query settlement windows, manage policy, and stream events over webhooks. Reach every counterparty on the network through a single integration.
# create a settlement obligation (devnet)
curl https://api.devnet.orrerysim.com/v1/obligations \
-H "Authorization: Bearer $ORRERY_API_KEY" \
-d '{"leg_deliver":{"asset":"BTC","amount":"2.5","to":"cpty_8f31"},
"leg_pay":{"asset":"USDC","amount":"162500","to":"self"},
"window":"next"}'