Transaction Submission Overview

This section introduces the transaction submission modes, including RPC, Block Builder, Transaction Sending, and Gas Sponsor, and explains how to choose the appropriate mode based on the scena

What is Transaction Submission

Transaction Submission is a collection of transaction submission capabilities in BlockRazor. Based on different transaction submission modes, it meets users' needs for fast transaction inclusion, gas sponsorship, MEV protection, and real-time rebates, providing a better trading experience and execution results for wallets, DEXs, Trading Bots, Searchers, and quantitative trading systems.

What are the modes of Transaction Submission?

RPC

RPC is the standard transaction submission entry point for Transaction Submission. Unlike ordinary public RPCs, BlockRazor RPC improves transaction speed and stability while providing private routing, MEV protection, and a refund mechanism, making it suitable as the default transaction channel for most businesses. BlockRazor RPC also provides a bundle submission entry point to meet the needs of scenarios such as Approve + Swap / Backrun / Copy Trading / Sniping.

Block Builder

Block Builder is the block building infrastructure provided by BlockRazor on BSC, supporting core capabilities such as bundle submission, private transaction submission, and bundle trace. It enhances block building competitiveness and block success rate through global deployment, low-latency communication with validators, and various block building algorithms.

Transaction Sending

Fast is the "speed-first" mode in Transaction Submission, suitable for scenarios highly sensitive to on-chain latency. It uses BEF to allow transactions to reach the block-producing node within a shorter time window.

Gas Sponsor

Gas Sponsor is a "cost-first" model within Transaction Submission. By paying gas fees on behalf of users, Gas Sponsor allows users to complete transactions without holding native tokens (such as ETH, BNB, and SOL), helping projects lower the barrier to entry for users and optimize trading experience.

How to choose the Transaction Submission mode

Scene	User	Mode
Protect against MEV attack and get refunds	Wallets / DEX	RPC - RawTransaction
Extreme speed boost and lower latency	Wallets / DEX / Trading Bot	Transaction Sending
No gas cost for users	Wallets / DEX	Gas Sponsor
Approve + Swap / Backrun / Copy Trading / Sniping	Wallets / DEX / Trading Bot / Searcher	RPC - Bundle

FAQ

What is the difference between submitting a Bundle to an RPC and submitting a Bundle to a Block Builder?

The core difference between the two lies in the different submission paths and final destinations of the Bundle. When submitting a Bundle to BlockRazor RPC, BlockRazor RPC forwards the Bundle to mainstream builders with low latency. This approach is more suitable as a unified access point, allowing users to submit Bundles without having to connect to different builders individually. When you submit a Bundle to Block Builder, the Bundle is sent directly to BlockRazor Builder. This is more suitable for scenarios where you explicitly want to use BlockRazor Builder capabilities and the access path.