{"action":"final","roles":[],"dispatch_reason":"","final_answer":"**The apparent discrepancy remains unresolved:** Trust’s published policy and attributed historical builder records describe different evidence; neither establishes today’s Trust route’s actual charge.\n\nTrust’s [support article](https://support.trustwallet.com/en/articles/717145-how-to-use-perpetuals-trading-perps-in-trust-wallet), displaying June 26, 2026, says standard Hyperliquid venue fees apply with no additional Trust platform fee. The supplied capture was retrieved October 29; its body was rechecked October 30. This is a current retrieved provider statement, not our observation of an app quote or execution.\n\nThe [pinned DefiLlama registry](https://github.com/DefiLlama/dimension-adapters/blob/51af729e8efd3360002f171fd2cd747cf4dbe8be/factory/hyperliquid.ts) maps builder `0x5af1b5f44207784dcb850bbb4143c5dcd1885f71` to Trust Wallet. That is third-party attribution, not provider attestation or proof of a frontend route, app version, or user session.\n\nSeven captured builder exports dated October 22–28 ([direct October 22 file](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261022.csv.lz4)) yield:\n\n`10,000 × 127,211.870597 / 127,213,257.389902 = 9.999891 bps`.\n\nThis is the **notional-weighted historical builder-fee ratio**, not an average of row rates. One bp is 0.01%. The numerator sums `builder_fee`; the denominator sums `px × sz`. Aggregation assumes compatible quote/collateral units because feeToken and historical market metadata are missing. The 44,528 rows include two zero-fee rows and 737 retained exact repeats; unique executions cannot be established. Captures end around midday UTC, so they are not seven complete days. Later credits/rebates and net user costs are unknown.\n\n**No current route-linked quote or execution was observed by us.** Historical records therefore cannot establish today’s Trust tariff or explain whether policy, route differences, or credits reconcile the apparent tension.\n\nFor the synthetic ordinary Tier-0 perp, the [base taker rate](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees) is 0.045% per side, without discounts. Exact dollar subtotals are:\n\n| Builder scenario | Venue: $10,000 entry | Venue: $10,500 exit | Builder, both sides | Trading-fee subtotal |\n|---|---:|---:|---:|---:|\n| Zero surcharge | $4.500 | $4.725 | $0.000 | **$9.225** |\n| Conditional 10 bps/side | $4.500 | $4.725 | $20.500 | **$29.725** |\n\nThe conditional builder amounts are $10.000 entry and $10.500 exit. This scenario is **not today’s Trust quote**. Subtotals exclude funding, execution shortfall, bridge/conversion, gas, activation, withdrawal, and rebates.\n\n[Builder documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes) specifies tenths of a bp: `f=10` means **1 bp**; `f=100` means **10 bps**. An approved maximum is a ceiling, not the per-order charged rate. The documented [userFills schema](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint) makes `fee` inclusive of `builderFee`; adding it again double-counts. These builder-only CSVs are a different format.\n\nWithout trading, resolution needs dated, version/route-specific provider clarification and an existing quote or unsigned order payload showing builder address/rate and fee breakdown. Those establish configured terms; an already-existing, redacted route-linked execution record with inclusive fees and any credits would establish an actual charge. None was supplied.","verification_notes":"Completed alone using 18 shared task calls: three skills, six sources, one aggregate, eight decimal calculations. No network requests, wallet connection, account query, signature, trade, or contact occurred.\n\nWeighted result: 9.9998909867626650301018814370362062496105190582799 bps, rounded to six decimals as 9.999891. Venue charges: 4.500 + 4.725 = 9.225 dollars. Conditional builder charges: 10.000 + 10.500 = 20.500 dollars. Combined subtotal: 29.725 dollars. Each side uses its own notional.\n\nPreserved distinctions: provider publication versus retrieval/recheck dates; third-party mapping versus route attribution; historical partial exports versus current execution; approval ceiling versus charged rate; builder CSV field versus inclusive userFills fee. Current route charges and historical net costs remain unestablished."}