- [Trust’s statement](https://support.trustwallet.com/en/articles/717145-how-to-use-perpetuals-trading-perps-in-trust-wallet), captured October 29 and body-rechecked October 30, 2026, says standard Hyperliquid fees apply without an additional platform fee. Historical exports attributed through a pinned third-party DefiLlama mapping create an unresolved discrepancy; they establish neither today’s app route nor wrongdoing. **No current route-linked execution was observed.**

- Aggregate arithmetic: `10,000 × 127,211.870597 / 127,213,257.389902 = 9.999891 bps`. This is builder fee divided by captured notional, weighted by notional; 1 bp = 0.01%. The 44,528 rows include two zero-fee rows and 737 retained exact repeats. Captures cover partial days, lack sufficient unique-execution identifiers and fee-token/market metadata, and assume compatible quote/collateral units. Rebates and net cost remain unknown. [Example export](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261022.csv.lz4).

- Synthetic ordinary, undiscounted Tier-0 taker arithmetic using [0.045% per side](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/fees):

| USD | Entry $10,000 | Exit $10,500 | Subtotal |
|---|---:|---:|---:|
| Venue | 4.500 | 4.725 | 9.225 |
| Conditional 10-bps builder | 10.000 | 10.500 | 20.500 |
| Combined | 14.500 | 15.225 | 29.725 |

Zero-builder subtotal: **$9.225**. Conditional subtotal: **$29.725**, not today’s Trust quote. Excludes funding, shortfall, bridge/conversion, gas, activation, withdrawal and rebates.

- [Builder rules](https://hyperliquid.gitbook.io/hyperliquid-docs/trading/builder-codes): `f=10` means **1 bp**; 10 bps requires `f=100`. Approval sets a ceiling, not the charged order rate. Perp cap: 0.1%, both sides; spot cap: 1%, excluding buys.

- [Documented userFills](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint) `fee` already includes `builderFee`; never add it again.

- Resolve current configuration without trading through dated provider clarification plus route/version-specific unsigned order payload showing builder and `f`. Execution itself remains unverified.