Quote.Trade public funding and position verification

Quote.Trade combines private bilateral execution with public smart-contract funding, published withdrawal balances, and public position-state infrastructure. Verification joins the funding and position layers at a common completed snapshot.

Official contracts

V6 funding core — Ethereum and XDC
0xfb41c4f731a064fb3911d16d529be0c2958d5fc6

V6 read-only views — Ethereum and XDC
0x228d706e0651038dd8ec151e2f639b3e47ffecb6

PositionManager — Polygon and XDC
0xf857aC7bed76B43c5457f56483803C4CebbD7eff

Cross-chain reconciliation map

Ethereum permissionless accounts
V6 Ethereum USDC/USDT assets and published balances
<-> corresponding completed Polygon PositionManager positions

XDC permissionless accounts
V6 XDC USDC assets and published balances
<-> corresponding completed XDC PositionManager positions

This mapping joins physical collateral, published account balances, positions, snapshot completeness, and completed withdrawals without publishing private orders or broader trading strategies.

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.

What each layer publishes

V6 funding core

• physical supported stablecoin balances;
• user-to-wallet registration;
• collateral composites and token membership;
• published user balances;
• historical withdrawal-cap observations;
• publication and pending-batch state;
• completed withdrawals and consumed withdrawal IDs;
• rate, cooldown, membership, role, and emergency state.

V6 views companion

• read-only status and balance exports;
• binary and CSV export surfaces;
• immutable linkage to the funding core;
• a canonical reporting path for V6 state.

Funding assets remain in the V6 core.

PositionManager

• user and wallet mappings;
• asset IDs, symbols, and quantity scales;
• per-user asset position quantities;
• snapshot identifiers and publication cadence;
• processed and total batch counts;
• completed position exports.

PositionManager is the public position-state layer on Polygon and XDC. Stablecoin custody remains in V6.

Point-in-time interpretation

A token balance in a funding contract at block T is the current amount held by that contract at T. Trading activity is recorded in private authenticated order and fill records. Executable liquidity is measured through current size-specific quotes and fill outcomes. Corporate treasury and Quote.Trade Pro custodian assets are measured through their corresponding records.

Snapshot alignment

Use one completed accounting snapshot:

1. Confirm chain, block, contract, token, and decimals. 2. Confirm the V6 core and views addresses are linked. 3. Confirm the V6 publication is complete. 4. Confirm PositionManager processedBatches == totalBatches. 5. Confirm lastSyncedTime is current relative to syncFrequency. 6. Match wallet, user ID, asset ID, symbol, quantity scale, composite ID, snapshot ID, and timestamp. 7. Use synchronized marks for the matching position snapshot.

User-level equation

published account equity
= recognized deposits
- completed withdrawals
+ realized P&L
+ unrealized P&L at synchronized marks
- funding paid
+ funding received
+ disclosed account adjustments

Each term is joined by the registered wallet and user ID. Position quantities come from PositionManager; physical funding and withdrawal transfers come from the stablecoin and V6 contract records; the published withdrawal balance comes from V6.

Aggregate coverage

Ethereum Grouped-Par USDC and USDT

Ethereum physical assets
= V6 Ethereum USDC balance
+ V6 Ethereum USDT balance

Ethereum published withdrawal obligation
= sum of positive current balances
  in the Ethereum USDC+USDT Grouped-Par composite

Ethereum coverage surplus
= Ethereum physical assets
- Ethereum published withdrawal obligation

Ethereum coverage ratio
= Ethereum physical assets
/ Ethereum published withdrawal obligation

XDC segregated USDC

XDC physical assets
= V6 XDC USDC balance

XDC published withdrawal obligation
= sum of positive current balances
  in the XDC USDC Segregated composite

XDC coverage surplus
= XDC physical assets
- XDC published withdrawal obligation

XDC coverage ratio
= XDC physical assets
/ XDC published withdrawal obligation

Gross leveraged notional measures market exposure. Positive published withdrawal balances measure the current stablecoin settlement obligation.

Completed-withdrawal verification

For each completed withdrawal:

1. Confirm the registered user wallet and composite. 2. Confirm the current completed position and balance snapshots. 3. Read published balance, cap basis, cap consumption, cooldown, membership, and emergency state. 4. Confirm physical token liquidity. 5. Confirm the unique withdrawal ID. 6. Confirm the balance and cap are consumed once. 7. Confirm the exact ERC-20 amount reaches the registered wallet.

V6 protection model

V6 uses a direct non-upgradeable core, separated operational roles, registered-wallet settlement, three qualifying observations at least 22 hours apart, a shared lowest-observation 1.5× cap, a ten-minute cooldown, complete multipart publication, replay protection, physical-liquidity checks, conditional velocity controls, exact unit conversion, exact debit/credit invariants, non-reentrant execution, timelocked composite membership changes, and emergency signer rotation.

Balance-publisher protection

The publisher can publish state but cannot independently execute a withdrawal. Newly published balances become withdrawal-relevant only after complete publications, three qualifying observations, the required time cadence, and the post-publication cooldown.

Withdrawal-execution protection

The withdrawal role pays the registered wallet and remains subject to the published balance, seasoned cap, unique withdrawal ID, completed snapshot, physical token liquidity, applicable velocity capacity, current signer epoch, and exact transfer invariants.

Admin, asset-manager, and emergency protection

V6 has no proxy upgrade path, so administrative action cannot replace the core implementation in place. Composite membership changes use a seven-day proposal process and completed post-change publication. Emergency mode begins a three-day freeze, rotates the signer epoch, refreshes affected roles, raises the history floor, and requires fresh cadence-valid observations.

These controls keep payout eligibility bound to completed, seasoned, and publicly inspectable state throughout normal and emergency operations, including when an operational credential requires containment and rotation.