A private market, with explicit boundaries.
OTConChain connects institutional block-trade requests with approved market makers. The proposed marketplace coordinates private invitations, independent quotes, client selection and execution evidence. Clients and makers retain their own trading keys and inventory.
Start with your role
- Institutions: define a mandate, choose eligible counterparties, review offers, authorize from your wallet and retain evidence. Read the institution guide.
- Market makers: expose a quote adapter, sign native orders and manage inventory, signer authority and outstanding exposure. Read the maker guide.
Architecture and responsibilities
| Participant | Responsibility | Authority retained |
|---|---|---|
| Institution | Trade mandate, counterparty selection and approval | Client wallet, sell assets and allowance |
| Market maker | Quote pricing, signing and inventory | Maker wallet, signer, risk limits and cancellation |
| OTConChain | Private transport, validation, ranking and records | Application access and prepared payloads |
| Existing 0x deployment | Native signature/condition checks and token exchange | Protocol rules and external upgrade administration |
The direct native route integrates an existing 0x contract; it does not depend on the hosted 0x Swap API. Verify the chosen deployment and required features before any live use.
What exists today
| Component | Status | What that means |
|---|---|---|
| Native RFQ code | Local prototype | Signing, validation, calldata and recorded local EVM execution |
| Multi-maker auction specification | Proposed interface v1 | Rules and downloadable local conformance kit; no hosted trading service |
| Onboarding | Application review | Public applications are prepared by email; the local preview can store test submissions |
| Original Sepolia MVP | Separate mock-asset demonstration | Earlier custom settlement contract and different authorization flow |
| Safe, custody and mainnet integration | Further implementation | Not established by the local prototype |
The October 14 prototype recorded 27 application checks and 18 isolated EVM checks. They are historical local results, not proof of a live maker connection. The newer local kit has its own conformance results.
Initial integration boundary
Start with one approved EVM chain, one standard ERC-20 pair and direct client EOA execution. The application requests a full fill of the selected quote; split allocation, partial fills, cross-chain execution, delegated trading and custom fee contracts are outside this initial design.
The original MVP’s signed customer intent and 80% minimum-fill option are not native 0x features of this integration. Do not carry those assumptions into an adapter.
Privacy and trust
Quote discovery is private to authorized participants and the platform operator. It is not cryptographically hidden from the operator. Native orders contain wallet addresses. Public chain settlement reveals addresses, tokens and amounts; transaction submission may reveal terms before inclusion. Protected transaction delivery is separate work.
Upstream protocol review does not audit the OTConChain application. An evidence hash checks integrity of a retained record, not best execution or complete quote capture.
Continue
Read the auction rules, inspect the API contract, then prepare your readiness packet. Every live environment requires a separately agreed configuration and joint acceptance.