The apparent discrepancy remains unresolved because the evidence covers different scopes.

[Trust’s support article](https://support.trustwallet.com/en/articles/717145-how-to-use-perpetuals-trading-perps-in-trust-wallet), dated June 26, 2026, says standard Hyperliquid fees apply with no additional platform fee. Its retained capture was retrieved October 29; the body was rechecked October 30. This is a current retrieved provider statement. **We observed no current route-linked quote or execution.**

The [pinned DefiLlama registry](https://github.com/DefiLlama/dimension-adapters/blob/51af729e8efd3360002f171fd2cd747cf4dbe8be/factory/hyperliquid.ts) maps the captured builder address to Trust. The [historical exports](https://stats-data.hyperliquid.xyz/Mainnet/builder_fills/0x5af1b5f44207784dcb850bbb4143c5dcd1885f71/20261022.csv.lz4) record builder charges under that third-party attribution. They do not identify the app version, frontend route or user session, or establish today’s net tariff after possible credits. They do not establish wrongdoing.

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 decimals; one basis point is 0.01%. It uses summed builder fees divided by summed `px×sz`, assuming compatible quote/collateral units. Missing `feeToken` and historical market metadata prevent verifying that assumption. October 22–28 captures cover partial days ending around midday UTC: 44,528 rows, including two zero-fee rows and 737 retained exact repeats. Unique executions and complete coverage are unverified; decimal precision does not remove those limits.

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

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

The conditional builder increment is $20.500. This is a scenario, not today’s Trust quote. Subtotals exclude funding, execution shortfall, transfers, gas 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**; **10 bps requires `f=100`**. Approval authorizes a maximum; the order specifies the charged rate. Documented [`userFills.fee`](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint) already includes `builderFee`; adding it again double-counts. Builder-only CSVs have a different scope.

Without trading, dated current-route/version evidence, an existing redacted unsigned order showing builder address/`f`, and matching fee-preview/credit terms could resolve intended pricing. Existing preserved route-linked execution evidence would be needed to establish actual charges.