Tokenized directional exposure requires a distinction between transferring a claim, requesting a position check, submitting an order and confirming a fill. This report examines a Solidity controller that organizes long and short leveraged claims into underlying-asset families, with a separate token and venue-custody contract for each direction and leverage tier. Every token update requests a family check; a compiled Uniswap v4 observer additionally requests checks for pool activity. Deposits can allocate equally across every enabled matched tier, with atomic settlement of the resulting claims. The evaluation inspects a pinned source snapshot and reruns two original local suites against a mock venue: 31 tests pass, including 256 inputs to one transfer-conservation fuzz test. The evidence covers escrow separation, cancellation, net fee minima, stale-report rejection, requested-versus-confirmed actions, partial-fill reconciliation and a 100-member family boundary. Transfer notifications produce no synchronous venue orders, the controller retains a 1 percent drift threshold, and claim-batch atomicity does not establish simultaneous fills or persistent economic neutrality. Valuation and venue-state confirmation depend on a trusted reporter. At unchanged value, the examined base policy reduces a 100-unit deposit to 94.08 units after entry and exit fees alone. The findings support bounded local accounting and coordination behavior, while leaving live integration, operational cost, usable exits and financial inclusion unmeasured. Jarett Dunn. Technical report, version 1.0. Preprint, not peer reviewed. Codex assisted source inspection, test orchestration and writing. The report text is CC BY 4.0; archived software retains its original licenses and attribution.
No takes yet. Share an insight, caveat, or question.
Jarett Dunn (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: