Discovery & Corridors#
TetraFi connects institutional participants through a corridor-based discovery model. Corridors define the routes, workspaces organize the participants, and the corridor registry matches them.
Corridor Model#
A corridor is a directed route: origin_chain:token → destination_chain:token. Each corridor has its own solver set, compliance requirements, and volume thresholds.
Directionrequired- Origin chain + token → Destination chain + token
Solver Set- Qualified solvers registered for this corridor
Compliance Level1–3- Minimum attestation tier required
Volume ThresholdUSD- Minimum order size for this corridor
Default Oracle- Oracle used for cross-chain attestation
Example Corridors#
| Corridor | Description |
|---|---|
base:usdc → optimism:usdt | Base USDC to Optimism USDT |
ethereum:usdc → arbitrum:usdc | Same-token cross-chain transfer |
optimism:usdt → base:usdc | Reverse direction (separate corridor) |
Corridors are directional - base:usdc → optimism:usdt and optimism:usdt → base:usdc are separate corridors with potentially different solver sets and pricing.
Corridor Distribution#
Example only. Real state varies - query GET /api/v1/corridors for the live registry.
Lock Type Per Corridor#
| Lock | Notes |
|---|---|
| ResourceLock | Output-first via The Compact; highest capital efficiency |
| Permit2Escrow | Input-first; one-time Permit2 approval |
| EIP-3009 | Gasless for USDC/EURC; no approval |
Lock type is exposed per corridor via GET /api/v1/corridors. See Settlement Flows for the full comparison.
Member Onboarding#
- Organization registers and completes KYC/KYB verification
- Admin creates one or more workspaces within the organization
- Workspace members are invited with role-based access (admin, trader, viewer)
- Corridors are configured per workspace based on compliance tier
- Credit lines are allocated per workspace
- API keys are generated for programmatic access (
tfk_live_.../tfk_test_...) - Integration begins: submit RFQs, receive quotes, execute settlements
Workspace Configuration#
Each workspace is independently configurable:
Active trading routes. Corridors are enabled per workspace based on the organization's compliance tier. Higher tiers unlock more corridors and larger volume thresholds.
Corridors can be enabled/disabled without affecting other workspaces in the same organization.
Solver Discovery#
Solvers register for specific corridors. When a taker submits an RFQ, the engine identifies all qualified solvers for that corridor and broadcasts the request.
Solver qualification depends on:
- Registration for the corridor
- Valid compliance attestation (if compliant corridor)
- Active WebSocket connection (for real-time quote delivery)
- Sufficient historical fill rate (solvers with poor reliability may be deprioritized)