Execution, balances & evidence
System ownership, the trade lifecycle and the path from private Testnet to client execution.
Clear boundaries make integration possible.
Each application connects to the system that owns the requested capability.
Identity
Hybrid ID establishes who is requesting access.
Execution
Exchange validates and executes trade instructions.
Accounting and custody
Core/MPC own balances, reservations and transfer authority.
Durable evidence
Chain/Explorer record and verify the appropriate evidence.
Identity begins the decision.
The execution boundary checks more than successful sign-in.
Personal requests
Verify the subject, account grant, product eligibility and limits.
Business requests
Verify membership, scoped roles and independent approvals.
Delegated applications
Banking acts through explicit delegation to Exchange, not an inferred shared session.
One spendable balance.
Reservations for orders and withdrawals must draw on the same authoritative funds.
Reserve
Core protects funds required by an admitted instruction.
Execute
Rust produces an ordered outcome; uncertainty retains protection.
Settle
Core applies fills, fees and valid releases exactly once.
Custody
MPC follows the authorized custody and transfer route.
Recovery is part of the workflow.
Lost replies and repeated delivery must not change the economic result.
Rust core
The only matching-engine direction; Python matching is being retired.
Kafka
Command/event delivery, sequencing and recovery connect the private services.
Reconciliation
Resolve uncertain outcomes against retained authoritative state.
Chain proofs
A completed match alone does not prove settlement or chain publication.
From private services to client acceptance.
Private synthetic checks are useful evidence, but they do not establish real customer readiness.
1 · Authority
Real identity mapping, account grants and Banking delegation.
2 · Funds
Canonical MPC unit-ledger reservations and balance checks.
3 · Runtime
Isolated Rust Testnet and durable Kafka delivery.
4 · Access
Authenticated gateway request/status and joined end-to-end acceptance.
Start from the contract and the owner.
Connect to the appropriate system and retain the identifiers that let outcomes be reconciled.
Exchange
Execution requests, provider terms and resulting status.
Core / MPC
Canonical accounts, deployment identities, balances and reservations.
Chain / Explorer
Publication references and verifiable evidence.
Use the slide buttons or left/right arrow keys. Escape exits full screen. Website and demonstrations available. Live trading and funding are not enabled.