One desk. One terminal.
One scoped pilot.
Connect the liquidity desk and trading terminal through a private RFQ workflow with explicit client approval.
Terminal → OTConChain
The terminal backend sends the exact terms for an enrolled institution. OTConChain checks access, freezes the request and contacts the approved desk.
One request ID · one immutable mandateThe CTO reading path
Pilot contract 0.1.0-draftPilot brief & acceptance
Scope, owners, delivery gates and the connection-day runbook.
Terminal & desk architecture
Account mapping, wallet authority, affiliation and private handoff.
Partner API contract
Scopes, exact operations, idempotency and polling recovery.
Lifecycle & evidence
Selection leases, cancellation, costs, finality and receipt semantics.
Prepare the same inputs.
Agree exact interfaces, fill the environment sheet and retain evidence against the shared test matrix.
Draft contracts and a client scaffold. Hosted services and joint acceptance remain required.
Docs, draft partner schemas, signed teaching fixtures and the maker conformance kit.
Owners, actual endpoints, tokens, wallets, timing, data visibility and acceptance limits.
Authenticated coordinator, terminal handoff, genuine desk service, wallet execution and reconciled evidence.
The first phase is single-maker. Disclose the affiliated desk/terminal roles; test independent competition only after separate consent and access-isolation checks.
Acceptance criteria