Stealth Mode Active

Private Bundles

Publicly broadcast trades can be visible to searchers. Where relay support applies, FRB routes transactions through Flashbots (EVM) and Jito (Solana) private relays to reduce public-mempool exposure before inclusion.

Review setup optionsRead the setup guideReview risk disclosure

See the AI-to-Execution Workflow — From a conversation to a plan you can review, approve and run.

Private Bundles

Prepare related operations in one reviewable submission workflow.

How you use it

Arrange operations, review settings and simulation, approve local signing, submit to the configured provider and inspect each outcome.

Before you start

Check supported chains, relay access, gas and expiry. Provider acceptance is separate from inclusion or confirmation.

Set up your bundle workflowAlready installed? Connect your agent

Local control. A clear execution workflow.

Configure supported operations on Windows, review the transaction path, sign locally and follow the submission result.

  1. Prepare the operation

  2. Review settings and preflight

  3. Approve local signing

  4. Submit to the configured provider

  5. Check the execution status

A submitted request is not a confirmed transaction. Availability depends on your release, network and provider; inclusion and returns are not guaranteed.

Get Started with FRB

Follow the request, not just the submit button

Check the response from your configured provider and then the network result. These are separate stages, not a promise of execution.

  1. Submitted

    The request was sent. A local click or progress indicator alone does not prove provider receipt.

  2. Accepted by provider

    The provider acknowledged the request. Acceptance is not block inclusion or transaction confirmation.

  3. Included and confirmed

    Verify the transaction receipt or network status and the confirmation level required by your workflow.

  4. Rejected, expired or unresolved

    Inspect the returned error and network state before retrying. Do not blindly resubmit an operation that may already have executed.

Public Mempool

  • ❌ Visible to everyone
  • ❌ Vulnerable to Sandwich Attacks
  • ❌ Gas Wars & Failed Txs

FRB Private Relay

  • ✅ Kept out of the public mempool where supported
  • ✅ Designed to reduce sandwich exposure
  • ✅ Simulated before bundle submission

Atomic Execution

Bundles target atomic execution, but inclusion and execution still depend on relay, builder, network, and transaction conditions.

1. Sign & Seal

You sign the transaction locally. FRB encrypts it before it leaves your machine.

2. Private Route

The bundle bypasses the P2P network and goes directly to benign builders (Flashbots, Jito, Beaver, Titan).

3. Private Inclusion

Private inclusion reduces public-mempool front-running exposure; builder and execution risks remain.

Common Questions

Does this cost extra gas?

Private relay routing does not add a separate FRB gas charge. Network fees and any relay or builder requirements vary, so review the current route settings before submitting.

Which chains are supported?

Availability depends on the chain, selected provider, and current relay support. Check the route options in the Agent before submitting a live bundle.

Ready to go invisible?

Download FRB Agent