Private Transactions
Private transactions on RibbleChain protect against Miner Extractable Value (MEV) by hiding transaction details from the public mempool, preventing front-running and other exploitative strategies. This guide explains how to submit private transactions for Layer 1 (L1) and Layer 3 (L3) rollups.
Why Private Transactions?
Private transactions:
- Hide sensitive data (e.g., trade amounts in DeFi) from MEV bots.
- Ensure fair execution by bypassing the public mempool.
- Integrate with RibbleChain's inclusion lists for prioritized ordering.
Prerequisites
- RibbleChain CLI:
npm install -g ribblechain-cli. - A smart wallet with $XRB tokens (see Creating a Smart Wallet).
- Access to the Sequencer API (see Sequencer API).
Step 1: Enable Private Transactions
Configure your wallet for private transactions:
ribblechain-cli wallet config --private-tx true