Shielded Trading

Shielded Trading protects you from front running and sandwich attacks when you swap tokens on decentralized exchanges (DEXs). 

Get Protected on Gnosis Chain

Sandwich Attacks

Sandwich attacks are a common and damaging form of Maximal Extractable Value (MEV) attacks. They inflate token prices by sandwiching your purchase between an attacker's buy and sell transactions, profiting at your expense.

Billions in Losses

Crypto traders have lost over $1.38 billion to front running and sandwich attacks on Ethereum since 2020. It acts like a hidden tax on regular traders, amounting to hundreds or even thousands of dollars over time!

Who’s at Risk of Attack?

Everyone. It's a misconception that only big whales are targeted. MEV attacks also target regular traders like you. Attackers will launch an attack even for a small profit, causing you to lose significant funds.

See if you’ve been sandwich attacked using MEV Scanner.

How Shielded Trading Makes MEV Attacks Virtually Impossible

Shielded Trading solves this by encrypting your transactions. It encrypts your transactions before they enter the public mempool, which is the waiting area for transactions before they are processed, making it impossible for attackers to see and take advantage of your transactions. 

Shielded Trading employs a decentralized system (threshold encryption) to prevent power concentration, making it an ideal solution for maintaining decentralization.

Learn more about the advanced encryption technology behind Shielded Trading.

Get Protected on Gnosis Chain

Add the Shutter custom RPC to your wallet to enjoy censorship resistance and protection against malicious MEV.

Add Automatically

Add Manually

  • Network name: Shutterized Gnosis Chain
  • New RPC URL: https://erpc.gnosis.shutter.network
  • Chain ID: 100
  • Currency symbol: XDAI
  • Block explorer URL (Optional): https://www.gnosisscan.io

Important: Current Limitations and Risks for Mainnet Implementation

While it’s a full mainnet implementation, there are currently a limited number of participating validators and Keypers, which may lead to longer transaction inclusion times. Additionally, there’s still a trust assumption with the RPC, and validators are not yet subject to slashing. In rare cases, some transactions may fail to be included in a block due to validator issues or re-orgs, and while these will be re-sent by the inclusion service, they could become vulnerable to front-running since their keys may already be released.

Subscribe to our blog and don't miss our next post!