**The apparent discrepancy remains unresolved for today’s Trust route.** The evidence separates three things:

- **Retrieved provider statement:** Trust’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 maker/taker fees apply with no additional Trust platform fee. The retained capture was retrieved October 29; its body was rechecked October 30. This is a provider statement, not an observed app quote.
- **Attributed historical records:** A [pinned DefiLlama revision](https://github.com/DefiLlama/dimension-adapters/blob/51af729e8efd3360002f171fd2cd747cf4dbe8be/factory/hyperliquid.ts) maps builder `0x5af1b5f44207784dcb850bbb4143c5dcd1885f71` to Trust Wallet. Captured builder exports dated [October 22](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261022.csv.lz4)–[28](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261028.csv.lz4) contain builder charges. That third-party attribution does not identify a frontend route, app version or user session.
- **Current route-linked execution observed by us:** None. No current quote, account query or new execution was observed.

The historical notional-weighted builder ratio is:

`10,000 × 127,211.870597 / 127,213,257.389902 = 9.999891 bps`.

Here the denominator is `Σ(px × sz)` and the numerator is `Σ(builder_fee)`. One basis point is 0.01%; this is approximately 0.1% of captured fill notional, not a round-trip rate or a current net customer tariff. 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 exact repeats retained because unique executions cannot be established. Each of the seven files ends around midday UTC; these are not seven complete days. Later rebates/credits are unknown.

Under [builder-code documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes), `f` uses **tenths of a basis point**: `f=10` means **1 bp**; `f=100` means **10 bps**. User approval sets a maximum per builder; an order’s actual charged rate can be lower. The perpetual builder cap is 0.1% (10 bps).

For the synthetic ordinary Tier-0 perp, both sides are taker at the undiscounted [base venue rate](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees) of 0.045%:

| Builder scenario | $10,000 entry fee | $10,500 exit fee | Trading-fee subtotal |
|---|---:|---:|---:|
| Zero surcharge | $4.500 | $4.725 | **$9.225** |
| Conditional 10 bps each side | $14.500 | $15.225 | **$29.725** |

The conditional case adds $20.500 in builder fees. **It is a scenario, not today’s Trust quote.** Subtotals exclude funding, execution shortfall, bridge/conversion, gas, activation, withdrawal and rebates.

The documented [`userFills`](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint) `fee` already includes `builderFee`; adding it again double-counts. These builder-only exports are a different schema.

Without executing a trade, resolving the current quote requires dated evidence tying the exact Trust app/version and Hyperliquid route to its fee disclosure and unsigned order builder address/`f`. Proving actual charging would additionally require an already-existing route-linked fill/receipt with inclusive fees and any credits. Provider clarification could reconcile scope or timing; those explanations remain unestablished.