Paper contents
I · Research question
A quote-currency match is not necessarily a closed position.
A long perpetual on one venue and a short perpetual on another can reference the same asset while using different multipliers, lot steps, funding schedules, valuation marks, and fee bases. Spending the same number of USDT at exit does not guarantee buying or selling the entry quantity. The residual exposure is not slippage; it is a different position.
The research question is therefore elementary but decisive: what accounting contract must hold before funding, execution, and price components can be summed without changing the position, event window, or evidence state? The answer is a common-base-quantity, event-attributed, scenario-keyed ledger—not a more sophisticated display of the latest rate spread.
Research 01 asks how executable net carry is measured. Research 02 asks how net-carry cases are framed. This paper asks whether the underlying ledger is closed and attributable in the first place.
Read Research 02: Framing Net Carry
II · Framework
One closed quantity. One event-attributed ledger.
The central identity is additive only after every component shares one scenario key. Price P&L is decomposed into basis change minus crossing; funding is added once per eligible event; four execution fees and other measured cash costs are deducted once. Crossing is already inside the four VWAPs and is not deducted again.
Quantity closure
Both legs use one feasible base quantity Q. Entry and exit each walk two books at that same Q; insufficient depth produces an incomplete fill, never a fabricated last-level execution.
Event-attributed funding
Expected event time, venue-recorded settlement time, and local receipt time remain distinct. Receipts and payments are enumerated symmetrically, with one-to-one record matching.
Scenario error attribution
A current-state scenario uses only information known at its timestamp. The later gap separates funding, basis, crossing, fee, and other-cost changes rather than becoming one undifferentiated “slippage” number.
Evidence and joint-risk semantics
Official cash, snapshot proxies, four-book paper values, and actual fills are not interchangeable. Covariance is not assumed to be zero, and a signed accounting vector is not a calibrated probability distribution.
NA is not zero, and a proxy is not official cash.
A verified empty funding event set supports zero. A missing settlement mark supports NA. A stablecoin-parity scenario is not realised USD profit, and an unchanged-current-state scenario is not a future fill.
III · Figures
Accounting controls, numerical illustrations, and their limits.
Scroll horizontally or use the arrows. Select a figure to inspect its details.
IV · Evidence boundary
Accounting validity is not out-of-sample performance.
The paper validates identities and rejection rules. It does not validate a return estimator, a forecasting model, or a live execution strategy. Three routes and two arms on one day cannot identify a win rate, an opportunity frequency, a portfolio Sharpe ratio, or a stable market effect.
Quantity closure, four-fill VWAP accounting, symmetric funding, B−X, scenario error budgets, NA propagation, covariance-sensitive variance, and final-objective consistency.
Six route-arm net-before-funding values range from −24.93 to −89.91 USDT. RSR funding is a frozen-mark proxy; BTC's zero is a verified empty event set. Exact account net is NA throughout.
No live fills, account fees, official settlement marks for RSR, independent pre-result timestamp, multi-day robustness, third-venue comparison, predictive out-of-sample result, confidence interval, or multiple-testing result.
Positive values mean that the unchanged-current-state scenario was too favorable; negative values mean that the subsequent paper result was better.
V · Limitations
A reproducible accounting contract—not a live-system specification.
- Instrument scope. Inverse, quanto, continuously accruing, specially adjusted, liquidated, and unresolved mixed-currency positions require separate adapters or NA/UNSUPPORTED.
- Execution scope. Public books do not model queue position, reaction, hidden liquidity, partial fills, financing, transfers, liquidation, or capital limits.
- Protocol scope. The local hash preceded entry, but the external receipt arrived after the version-2 freeze and short-arm result. Independent pre-result timestamping remains outstanding.
- Reproduction scope. The package recomputes summary tables and deterministic tests. Raw archived books were not supplied, so raw-book replay is not claimed.
- Statistical scope. No predictive estimator or candidate model set is defined; out-of-sample tests, multiple-testing controls, and dependence-aware inference remain future work.
This paper is for research and methodological information only. It does not provide investment, legal, accounting, or tax advice; does not recommend any trade, venue, leverage, or position size; and does not promise income, execution, capital protection, or protection from liquidation.