How to Submit Private Transactions Without Tips

Learn how to submit a private transactions directly to block builders, protecting you from MEV extraction until it's included in a block.

When you submit a transaction to the public mempool, it's visible to everyone. MEV bots can:

  • Sandwich your trade — Place orders before and after yours to extract value

  • Front-run you — Copy your trade and execute it first

  • Back-run you — Profit from the price impact you create

Meanwhile, Private transactions eliminate this exposure by hiding your transactions until they are included.

Private TX vs Public Mempool

Aspect
Public Mempool
Private TX

Visibility

Everyone sees it

Only builders see it

MEV exposure

Vulnerable

Protected

Inclusion speed

Gas price dependent

Builder dependent

Best for

Speed-competitive scenarios

Value-sensitive trades

When to Use Private Transactions

Use private transactions when:

  • Executing large swaps that could be sandwiched

  • Trading tokens with low liquidity

  • Running strategies you don't want copied

  • Protecting any transaction from front-running

API Reference

Quickstart

1

Set up the project

2

Set the ES module "type": "module" in your package.json.

3

Create a file and name it index.js

4

Add the following code to index.js:

5

Import the dependencies

6

Create and Sign Your Transaction

7

Submit Privately

8

Response

chevron-rightComplete Example: Private BNB Transferhashtag
chevron-rightComplete Example: MEV-Protected PancakeSwap Tradehashtag

Selecting Specific Builders

By default, mev_builders: ['all'] sends to all available builders. You can target specific builders instead:

Available builders vary by network conditions. Use ['all'] for maximum inclusion probability.

Troubleshooting

Problem
Solution

Transaction not included

Without a priority tip, private transactions compete based on gas fees alone. If your transaction isn't being included:

  • Increase gas price — Higher gas = higher priority for builders

  • Add a priority tip — See Private Transactions with Tips

  • Try specific builders — Some builders may be more responsive

"Invalid transaction"

  • Verify your transaction is properly signed

  • Check the chain ID is 56 (BSC Mainnet)

  • Ensure the nonce is correct

Connection issues

  • Verify your API key is valid

  • Check network connectivity

  • Try reconnecting after a few seconds

Next Steps

To increase inclusion priority for your private transactions, see Private Transactions with Tips.

Last updated

Was this helpful?