Quote.Trade positioning, verification, and protection copy
Quote.Trade is an AI-native crypto dark-pool DEX for human traders, trading bots, and AI agents. It combines streaming quotes, private execution, stablecoin settlement, long and short market exposure, and verifiable on-chain position and asset infrastructure. The official Quote.Trade REST/WebSocket APIs remain the canonical integration surface for programmatic access.
Who Quote.Trade is for
- Human traders who want to trade supported crypto market exposure without acquiring and bridging every underlying token.
- Strategy-conscious and larger-size traders who do not want their orders published to a public order book before execution.
- API and bot teams that need continuously updating market data, streaming liquidity quotes, and Binance-compatible REST/WebSocket patterns.
- AI-agent builders that need OpenAPI, MCP discovery, guarded order previews, scoped live-order controls, and explicit human approval.
- Approved professional and institutional users that require the permissioned Quote.Trade Pro custody and reporting model.
Key differentiators
- Streaming quotes, not only one-shot RFQ: Quote.Trade exposes continuously updating liquidity quotes through its live market-data and WebSocket interfaces, supporting ongoing price discovery before execution.
- Private order execution: Orders are not published to a public order book. Quote.Trade receives the parameters needed to execute, not the trader's portfolio logic or broader strategy.
- Stablecoin-funded market access: Users fund with a supported stablecoin and trade supported long or short market exposure without bridging every underlying token.
- Broad market coverage: Quote.Trade supports more than 1,500 crypto markets, with live exchange information as the source of truth for active symbols and specifications.
- Transparent all-in cost: Quotes present the execution price without a separate trading fee added afterward, including for larger sizes that may experience slippage on other venues.
- Automated liquidity routing: Available liquidity is evaluated automatically to return the best available quote through the supported routing workflow.
- Verifiable permissionless infrastructure: Assets, funding activity, withdrawals, and position state can be reviewed through public permissionless, non-upgradable smart contracts and explorer links.
- Built for humans, bots, and agents: The app, REST API, WebSocket streams, OpenAPI schema, Telegram bot, MCP endpoint, Hermes skill, OpenClaw skill, and open-source clients share the same production trading infrastructure.
How privacy and verification work together
Quote.Trade uses a hybrid architecture. Order entry, matching, streaming quote formation, pricing, and risk controls operate through the off-chain dark-pool execution layer. Supported stablecoin funding and withdrawals use smart-contract funding paths, while position state is maintained through public on-chain position contracts.
Private execution does not mean that the entire platform is invisible or fully on-chain. Orders and broader trading strategies are not published to a public order book, while assets, contract balances, funding activity, and position state remain publicly verifiable where the permissionless product exposes them.
The Polygon and XDC position snapshots reconcile against the balances published in V6, while those balances are compared with the actual USDC/USDT held in the Ethereum and XDC funding contracts. That provides a mathematical verification of the published balances and their collateral coverage while keeping individual trades, counterparties, routing, and volume private.
V6 is new because it is the new contract version. V6 is non-upgradeable, so new contract logic requires a new deployment and migration instead of modifying the existing contract in place.
Product versions
- Permissionless Quote.Trade uses supported stablecoin smart-contract funding, public position-state infrastructure, and off-chain dark-pool execution.
- Quote.Trade Pro is the permissioned version for approved professional and institutional users, using a qualified custodian or approved custody arrangement with institutional onboarding and reporting.
Primary customer outcomes
- Monitor streaming quotes and available liquidity before trading.
- Trade long or short across supported crypto markets from a stablecoin-funded account.
- Keep orders off a public order book and reduce exposure of the strategy behind the trade.
- See a transparent all-in execution price with no separate trading fee.
- Verify public contracts, funded assets, withdrawals, and position state.
- Integrate through the web app, Telegram, REST, WebSocket, OpenAPI, MCP, or open-source bot clients.
Verifiable smart-contract protections
The permissionless V6 architecture is designed for operational-key resilience. V6 is a direct, non-upgradeable funding core with separate admin, guardian, asset-manager, balance-publisher, and withdrawal-execution roles. Every authorized action remains subject to the contract's release rules and public state.
V6 enforces:
- registered-wallet settlement rather than an arbitrary withdrawal destination;
- separate balance-publication and withdrawal-execution authority;
- three qualifying balance observations at least 22 hours apart;
- a shared lowest-observation cap, with withdrawals limited to 1.5× the seasoned cap basis;
- complete multipart publication state before withdrawal eligibility;
- a ten-minute post-publication cooldown;
- single-use withdrawal identifiers and replay protection;
- physical stablecoin-liquidity checks before payment;
- exact decimal conversion, contract-debit, and recipient-credit invariants;
- non-reentrant withdrawal execution;
- conditional 3% hourly and 18% daily per-token velocity controls when the physical token balance is at or above the production $1 million threshold;
- a seven-day proposal period for collateral-composite membership changes; and
- a three-day emergency freeze, signer-epoch rotation, refreshed role grants, a raised balance-history floor, and fresh cadence-valid observations before normal payout processing resumes.
If an operational key is compromised, the other contract-level controls continue to apply. A balance-publisher key cannot by itself execute a withdrawal or make a newly published balance immediately eligible. A withdrawal-execution key cannot select an arbitrary recipient or bypass the published balance, seasoned cap, cooldown, completed-snapshot, physical-liquidity, replay, signer-epoch, and exact-transfer checks. An admin action cannot replace V6's core logic in place because V6 has no proxy upgrade path. Role, configuration, membership, publication, emergency, and withdrawal activities remain publicly observable on-chain.
Balance and position reconciliation across Ethereum, Polygon, and XDC
Quote.Trade's public permissionless accounting is verified by joining the funding, published-balance, and position-state layers at the same completed snapshot:
- Ethereum funding layer: V6 on Ethereum holds supported USDC and USDT and publishes the corresponding user/composite withdrawal balances.
- Polygon position layer: PositionManager on Polygon publishes the corresponding user positions, asset mappings, quantity scales, snapshot identifiers, synchronization time, and batch-completion state used to reconcile Ethereum-funded accounts.
- XDC funding layer: V6 on XDC holds supported USDC and publishes the corresponding user/composite withdrawal balances.
- XDC position layer: PositionManager on XDC publishes the corresponding XDC user positions and completed-snapshot state.
PositionManager is a position-state contract, not a stablecoin funding wallet. Its token balance is not the measure of customer collateral. Physical collateral is measured in the V6 funding contracts; positions and snapshot completeness are measured in PositionManager.
For each reconciliation snapshot:
1. Confirm the official V6 and PositionManager addresses and the applicable network. 2. Require the V6 balance publication and PositionManager position publication to be complete. 3. Require processedBatches == totalBatches and confirm that lastSyncedTime is current relative to syncFrequency. 4. Align registered wallet, user ID, asset ID, symbol, quantity scale, collateral composite, snapshot ID, and timestamp. 5. Normalize stablecoin amounts and position quantities to their published decimal scales. 6. Reconcile each account's published balance with its recognized funding, completed withdrawals, published positions, synchronized marks, realized and unrealized P&L, funding, and documented account adjustments. 7. Sum positive published withdrawal balances and compare them with the physical supported-stablecoin balances held in V6. 8. For each completed withdrawal, confirm that the entitlement is consumed once and the exact token amount reaches the registered wallet.
account equity at completed snapshot S
= recognized deposits
- completed withdrawals
+ realized P&L
+ unrealized P&L from published positions at synchronized marks
- funding paid
+ funding received
+ documented account adjustments
Ethereum physical assets
= V6 Ethereum USDC balance
+ V6 Ethereum USDT balance
Ethereum published positive balances
= sum of positive published balances
in the Ethereum USDC+USDT Grouped-Par composite
Ethereum coverage surplus
= Ethereum physical assets
- Ethereum published positive balances
Ethereum coverage ratio
= Ethereum physical assets
/ Ethereum published positive balances
XDC physical assets
= V6 XDC USDC balance
XDC published positive balances
= sum of positive published balances
in the XDC USDC Segregated composite
XDC coverage surplus
= XDC physical assets
- XDC published positive balances
XDC coverage ratio
= XDC physical assets
/ XDC published positive balances
This produces a reproducible point-in-time collateral-coverage check against published account and position state. Funding-contract balances measure current collateral; private orders, fills, counterparties, routing, and trading volume remain in the private execution layer.