The apparent discrepancy remains unresolved: the provider statement, attributed historical records, and current execution evidence have different scopes.

**Provider statement.** [Trust’s support article](https://support.trustwallet.com/en/articles/717145-how-to-use-perpetuals-trading-perps-in-trust-wallet) says standard Hyperliquid maker/taker fees apply and Trust charges no additional platform fee. It displays June 26, 2026; the packet records retrieval October 29 and a body recheck October 30. This establishes the retrieved provider statement, without establishing a current app quote or executed charge.

**Historical records.** A [pinned DefiLlama revision](https://github.com/DefiLlama/dimension-adapters/blob/51af729e8efd3360002f171fd2cd747cf4dbe8be/factory/hyperliquid.ts) maps builder `0x5af1b5f44207784dcb850bbb4143c5dcd1885f71` to Trust Wallet. That is third-party attribution, without provider attestation or identification of a frontend/session. Captured exports span [October 22](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261022.csv.lz4)–[October 28](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261028.csv.lz4), 2026.

The supplied aggregate gives:

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

This is the notional-weighted historical builder-fee ratio, rounded to six decimal places. One bp is 0.01%; the denominator sums `px × sz`. It is neither an annual rate nor a complete venue-plus-builder fee rate. Compatible quote/collateral units are assumed 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. Each file ends around midday UTC, so coverage is seven partial days. Later credits/rebates and net user costs are unknown.

**Current execution.** We observed no current route-linked execution. These records cannot establish today’s Trust surcharge or resolve the statement’s historical applicability. They do not support an inference of wrongdoing.

For the synthetic ordinary, undiscounted Tier-0 perp, the [base taker rate](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees) is 0.045% on each side’s own notional:

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

The conditional builder component is $10.000 + $10.500 = $20.500. This is a scenario, not today’s Trust quote. Subtotals exclude funding, execution shortfall, bridge/conversion, gas, activation, withdrawal and rebates.

[Builder documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes) specifies tenths of a bp: `f=10` means **1 bp**; **10 bps** requires `f=100`. User approval sets a maximum; the actual per-order rate can differ. Under the documented [userFills schema](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint), `fee` already includes `builderFee`: adding it again double-counts. These builder-only CSVs are a different format.

Without trading, preserved, dated evidence linking a current Trust app/version and Hyperliquid route to an itemized pre-sign quote and unsigned order payload (`builder` address and `f`) would establish the quoted configuration. An existing route-linked fill record would establish an actual charge. Approval ceilings alone cannot do either; executed current charges remain unobserved here.