Trading fees on LeverUp are 57% lower. This is a protocol update, not a promotion — and the distinction matters.
The reduction didn't come from a manual fee schedule change or a time-limited campaign. It's a structural output of the Pyth Pro oracle upgrade that went live earlier this month. The infrastructure improved. The cost of trading went down with it.
The Mechanism Behind the Number
To understand why fees dropped, it helps to understand what fees are pricing in.
On a perp platform that uses oracle-referenced pricing, every trade execution, mark-to-market, and liquidation check references an external price feed. The fresher that feed, the more accurately it reflects current market conditions. The staler it is, the more uncertainty the protocol is operating with at the moment of execution.
That uncertainty has a cost. It shows up in how the protocol sets its execution parameters — and, downstream, in the fees traders pay.
When LeverUp upgraded to Pyth Pro, measured price feed staleness dropped from 1.676 seconds (Pyth Core) to 0.086 seconds — a 19.5× improvement in feed freshness. 91.4% of Pyth Pro samples registered zero measured staleness. The protocol is now referencing substantially fresher data during execution.
Fresher data lets the protocol operate with less built-in margin for pricing uncertainty. When that margin tightens, execution friction across the stack decreases — specifically, the spread buffer and risk parameters that the fee structure is built around. The 57% reduction is what that infrastructure tightening looks like in practice.
What Changes for Traders
Entry and exit fees have been reduced across supported markets. Fees are one of the few costs traders can see directly. A 57% reduction means a meaningfully lower break-even threshold on every position — less ground to recover before a trade is in profit.
The effect compounds across frequency and leverage. For traders running multiple positions or working at high leverage, fees accumulate quickly. A structural reduction of this size changes the math on strategies that were previously borderline — high-frequency approaches, tight mean-reversion setups, or frequent size adjustments that were fee-sensitive.
The scope is broad. Per the protocol announcement, the reduction applies across all markets, both taker and maker. This isn't a rebate on a specific pair or a discount for a specific trade type.
It is an ongoing protocol-level reduction, not a time-limited promotion. The 57% reduction follows from the Pyth Pro upgrade, which is a live infrastructure change. It holds as long as the infrastructure it came from holds — it isn't tied to a campaign window or a promotional period.
Why Infrastructure Drives Fees
The relationship between oracle quality and fee structure isn't always obvious, but it's direct.
On orderbook venues, market makers set spreads based on their own information asymmetry risk. On oracle-referenced venues like LeverUp, the fee structure is shaped by execution parameters that reflect the quality of the underlying price data. Specifically: how much buffer the protocol needs to build in to account for stale-pricing risk at the moment of execution. Better data compresses that buffer. Tighter parameters mean lower fees.
The Pyth Pro upgrade is documented in detail in the oracle upgrade article, including the methodology, the raw staleness data, and the consistency analysis across 370 parallel samples. The short version: Pyth Pro is the institutional tier of the Pyth oracle network, operating with higher publish frequency and tighter timing guarantees than Pyth Core. For a perp venue running at high leverage, the gap between those two tiers is meaningful.
LeverUp uses a protocol-managed virtual liquidity architecture powered by the VMMV, where trades reference oracle pricing while execution, settlement, and risk management are handled at the protocol layer. Improvements in oracle data quality flow directly through to the trading experience: execution, settlement, and risk management are handled at the protocol layer rather than depending on an externally supplied LP pool, so there's no intermediary layer absorbing the benefit before it reaches traders.
Protocol Efficiency as a Trader-Facing Outcome
The framing on the announcement graphic says "Better protocol efficiency. Lower trader friction. More value returned to active traders."
That sequence is the actual mechanism. Protocol efficiency isn't an abstract operational metric — it translates into the cost structure traders operate under. When the protocol runs on better infrastructure, the improvement flows to the people using it.
The 57% fee reduction is one of the clearer examples of that translation being measurable and immediate.
Pyth Pro is live. The fees reflect it.
Trade on LeverUp: app.leverup.xyz