Hybrid ID
Identity and sign-inAn application signs users in through the existing identity authority.
Connect to the execution layer.
Connect identity today and explore the intended Exchange workflows. Exchange execution contracts will follow with the backend release.
Hybrid ID sign-in is connected. Exchange trading APIs, SDKs and executable examples are not published by this website release.
Hybrid Exchange
Validation, execution and liquidityBanking and other applications request execution from the Exchange.
Hybrid Chain
Durable evidence and finalityChain records preserve evidence of completed lifecycle events.
Hybrid Explorer
Evidence inspection and proofsExplorer exposes the evidence for validation.
Integrate identity
Use the existing Hybrid ID developer portal for application registration and sign-in documentation.
Hybrid ID developer portalExplore ecosystem APIs
The Hybrid-Chain API reference documents ecosystem services. It is not an Exchange trading API contract.
Hybrid-Chain API referenceReview the workflows
Walk through orders, funding, approvals and evidence before implementing Exchange execution contracts.
Explore the demosWhat will connect next?
Exchange contracts will define order and quote requests, balance reservations, funding, approvals and lifecycle events. The future matching core uses Rust, with Kafka supporting event distribution. Python is not the Exchange execution path.
Execution, settlement and Chain evidence will remain distinct. The visual simulator becomes genuine Testnet practice when those services are connected.
Discuss an integration