Trust’s published statement and the attributed historical exports show an unresolved discrepancy; they do not establish today’s Trust surcharge.

- **Current retrieved provider statement:** [Trust’s Hyperliquid support article](https://support.trustwallet.com/en/articles/717145-how-to-use-perpetuals-trading-perps-in-trust-wallet), displaying June 26, 2026, says standard venue fees apply with no additional Trust platform fee. The retained bytes were retrieved October 29; the 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 exports contain builder fees. That third-party attribution does not establish provider ownership, app version, frontend route or any particular user session.
- **Current execution observed by us:** None. The packet contains no current route-linked quote or execution, wallet connection, account query or rebate/credit observation. It cannot establish current net user cost or wrongdoing.

The seven captured export files dated October 22–28, 2026—see [October 22](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261022.csv.lz4) and [October 28](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261028.csv.lz4)—give:

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

This is the notional-weighted historical builder-fee ratio, not an average of row rates. One basis point equals 0.01%. Aggregation assumes compatible quote/collateral units; `feeToken` and historical market metadata are missing. The 44,528 rows include two zero-fee rows and 737 retained exact repeats because unique executions cannot be established. Files end around midday UTC, so coverage is not seven complete days. Subsequent credits/rebates are unknown.

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

| Trading fees, USD | Entry $10,000 | Exit $10,500 | Subtotal |
|---|---:|---:|---:|
| Base venue fees | 4.500 | 4.725 | 9.225 |
| Zero builder surcharge: total | 4.500 | 4.725 | **9.225** |
| Conditional 10-bps builder component | 10.000 | 10.500 | 20.500 |
| Conditional combined total | 14.500 | 15.225 | **29.725** |

The 10-bps case is a scenario, not today’s Trust quote. These exact subtotals exclude funding, execution shortfall, bridge/conversion, gas, activation, withdrawal and rebates.

[Builder documentation](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes) defines `f` in tenths of a basis point: `f=10` means **1 bp**; `f=100` means **10 bps**, or 0.1%. An approved maximum is a ceiling; the order’s actual rate can differ. Neither approval nor the protocol cap establishes a charged rate.

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 CSVs have a different schema.

Without a new trade, dated route/version/market-linked unsigned quotes or order payloads showing builder address, `f` and fee breakdown, plus provider clarification of scope and timing, could resolve current configured pricing. Actual charged/net cost would require an already-existing route-linked receipt and applicable credit/rebate records.