Trezor has rolled out a new MEV protection feature inside Trezor Suite, aiming to make crypto transactions more reliable for users interacting with supported blockchain networks. The feature is now available directly in the company’s desktop application and is designed to reduce harmful transaction manipulation such as front-running and sandwich attacks. According to the company, the initial rollout covers Ethereum, BNB Chain, and Base.
The update reflects a practical approach to wallet security: rather than asking users to install separate tools or modify their behavior, Trezor has built the protection into the normal transaction flow. The company said the system routes transactions through private channels so pending orders are less exposed to bots that monitor public mempools for profit opportunities.
How the New Protection Works
MEV, or maximal extractable value, refers to the value that can be captured by reordering, inserting, or censoring transactions before they are finalized onchain. In practice, that often means users can be disadvantaged by automated bots that detect pending swaps and attempt to profit from them. Trezor said its newly integrated protection is intended to limit that exposure by obscuring transactions before they reach a public mempool environment.
Because the feature is embedded directly into Trezor Suite, the process is meant to happen automatically. Users do not need to change their basic workflow when sending funds, swapping tokens, or trading assets. Trezor said the result should be lower slippage, fewer failed transactions, and more predictable execution, especially in situations where public visibility of a pending transaction could trigger adverse bot activity.
The private routing component behind the feature is powered by Merkle.io. Trezor described the partnership as part of a broader effort to deliver meaningful improvements to user safety without adding friction to the self-custody experience.
Targeting Front-Running and Sandwich Attacks
Trezor specifically said the protection is meant to defend users against common exploitative order-flow behavior associated with MEV on public mempools. Two of the main attack patterns named by the company are front-running and sandwich attacks.
In a front-running scenario, a bot sees a pending transaction and submits its own transaction first in order to gain a pricing advantage. In a sandwich attack, a bot places one trade before a user’s transaction and another immediately after it, profiting from the price movement created by the user’s order. For retail users, these tactics can result in worse execution prices and unexpected outcomes, particularly during token swaps in volatile markets.
By reducing transaction visibility before confirmation, Trezor is trying to make those attack strategies harder to execute against Suite users. Importantly, the company said this is done while preserving normal Suite workflows and existing fee selection behavior for supported networks.
A Security Upgrade Built Into the Wallet Experience
Trezor framed the release as another example of practical software-side security development. Instead of positioning MEV protection as an advanced optional feature for power users only, the company is treating it as an integrated part of the wallet environment. That approach aligns with a larger trend in crypto product design, where infrastructure-level protections are increasingly being embedded into mainstream consumer tools.
Lauri Hänninen, Trezor’s product marketing lead, said the rollout is intended to give users “greater confidence and control” when moving funds through Trezor Suite. That language suggests the company sees transaction quality and predictability as an important part of wallet security, not just custody of private keys.
This distinction matters because self-custody products are no longer judged solely by how well they store assets. Users also expect better protection during actual onchain interactions, where losses can occur not from wallet compromise but from poor trade execution, failed swaps, and manipulative market behavior.
Part of Trezor’s Broader Self-Custody Strategy
Trezor linked the launch to its longer-term mission of promoting self-custody through open-source tools, a direction the company says it has followed since 2013. Over the years, Trezor has expanded beyond hardware wallets into a wider mix of software products and educational initiatives.
The company also pointed to efforts such as Trezor Academy, which are designed to improve user understanding of crypto security and self-custody. In that context, MEV protection can be seen not as a standalone feature but as part of a broader push to make crypto usage safer and more accessible for mainstream users.
At the same time, Trezor did not provide details on whether the feature will expand to additional blockchains in future releases. It also did not say whether users will eventually be able to configure the routing mechanism manually. For now, the protection is available immediately within Trezor Suite on the three announced networks.
What the Launch Means for Users
For current Trezor users, the immediate significance of the update lies in transaction reliability. On networks where MEV activity is common, a private routing layer can help shield users from some of the most visible and frustrating consequences of public mempool exposure. That includes not only predatory pricing but also the execution uncertainty that often comes with competitive blockspace environments.
While the company has not published additional technical details in this announcement, the basic value proposition is clear: make routine crypto transactions less vulnerable to bots without forcing users to learn new tools or adopt more complicated workflows. In an industry where security often comes at the cost of usability, Trezor is presenting this update as an attempt to improve both at the same time.
With MEV protection now live in Trezor Suite, the company is adding another layer to its wallet ecosystem—one focused less on asset storage and more on what happens in the critical moments when users actually transact onchain.