Files
proxmox/docs/03-deployment/CRYPTO_COM_OTC_BEFORE_AFTER_OPERATOR_MATRIX.md
defiQUG 4fab998e51
All checks were successful
Deploy to Phoenix / deploy (push) Successful in 9s
chore: sync workspace docs, configs, and submodules
2026-04-18 12:07:15 -07:00

5.4 KiB

Crypto.com OTC Before Vs After Operator Matrix

Last Updated: 2026-04-17
Purpose: Strict operator comparison of the current ecosystem state versus the state after a real Crypto.com OTC destination is connected as the off-chain execution sink.

Scope

  • This matrix is grounded in the current repo-generated artifacts, especially:
    • reports/extraction/comprehensive-capital-baseline-latest.json
    • reports/extraction/source-to-cex-execution-plan-latest.json
    • reports/extraction/source-to-cex-production-readiness-latest.json
    • reports/extraction/immediate-and-same-day-corridor-assets-latest.json
  • It does not assume any undocumented Crypto.com OTC limits, settlement terms, or acceptance rules.
  • “After” means: a real off-chain sink row exists, it is enabled for production handoff, the deposit asset and address are configured, and production is intentionally promoted.

Strict Matrix

Dimension Before Crypto.com OTC After Crypto.com OTC
Terminal sink model Public Mainnet cW-to-canonical pools Mainnet normalization plus external OTC execution
True size absorber cWUSDC -> USDC pool Crypto.com OTC books / negotiated execution
Strongest verified direct public normalization depth About $213.10 via cWUSDC -> USDC Still about $213.10 on-chain, but no longer the system-wide economic cap
Direct cWUSDT -> USDT depth About $2.18 Still about $2.18; remains weak unless separately improved
Immediate bucket (cWUSDC, cWUSDT) About $17.78M, but operationally constrained by shallow public exits About $17.78M, now potentially executable through bounded normalization and OTC handoff
Same-day corridor bucket (cUSDC, cUSDT, stable LP feeders) About $1.381B, structurally ready but terminally constrained About $1.381B, now becomes a credible same-day institutional feeder set if OTC handoff is live
cUSDC operating path cUSDC -> bridge -> cWUSDC -> USDC, then stalls on shallow public sink cUSDC -> bridge -> cWUSDC -> USDC -> Crypto.com OTC
cUSDT operating path cUSDT -> bridge -> cWUSDT -> cWUSDC -> USDC, still bottlenecked by public sink cUSDT -> bridge -> cWUSDT -> cWUSDC -> USDC -> Crypto.com OTC
Stable LP role LPs are strong feeder-prep assets, but not meaningful exits on their own LPs become materially more useful because unwind can feed a real external execution rail
On-chain Mainnet role Expected to absorb trade size Reduced to a bounded conversion handshake before OTC handoff
Main system bottleneck Terminal public liquidity concentration Off-chain execution onboarding, deposit correctness, operational governance, and settlement workflow
Planner posture multi-path -> single shallow sink multi-path -> normalized settlement asset -> OTC sink
Readiness blocker No real off-chain sink included; production disabled Remaining blocker becomes real-world OTC setup quality, not architecture
Risk concentration DEX liquidity and slippage Counterparty, deposit rail, packet policy, reconciliation, and execution controls
Operator dependency Public PMM liquidity OTC account activation, accepted asset, deposit address, and operating limits
Repo readiness state offchain_sink_defined = blocked; live_production_enabled = blocked Can become ready after sink row + enablement + production promotion

Practical Reclassification

If Crypto.com OTC is connected as a real sink, the ecosystem does not become richer in nominal terms. It becomes more executable.

  • Before:
    • large corridor inventory
    • tiny public terminal sink
    • strong routing structure but weak external realization
  • After:
    • same inventory
    • same bridge and normalization structure
    • materially improved ability to hand same-day corridor assets into external institutional liquidity

What Changes Operationally

Asset Group Before After
cWUSDC Immediate in mechanics, but shallow public exit Immediate normalization asset for OTC deposit preparation
cWUSDT Immediate in mechanics, but direct USDT path is too shallow Usually normalize through USDC, then hand to OTC
cUSDC Best same-day corridor feeder, but ends at weak public sink Best same-day corridor feeder into OTC
cUSDT Same-day feeder, but practically dependent on USDC normalization Same-day feeder into OTC after USDC normalization
Stable LP claims Preparation only Preparation plus real external execution path
Non-promoted assets Still not standard feeders Still not standard feeders unless separately promoted

Readiness Gate

The repo should still treat the system as not live until all of the following are true:

  1. A real Crypto.com OTC row exists in config/extraction/additional-wallet-inventory.json.
  2. include_in_baseline is true.
  3. enabled_for_production_handoff is true.
  4. operational_status is enabled.
  5. Deposit asset, chain, and address are populated.
  6. config/extraction/source-to-cex-production-policy.json is intentionally set to production_enabled: true.

Bottom Line

Before Crypto.com OTC, the ecosystem is best described as:

large inventory + good corridor structure + shallow public terminal sink

After Crypto.com OTC, it becomes:

large inventory + good corridor structure + bounded Mainnet normalization + real external execution destination