> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/transaction-submission/transaction-sending.md).

# Transaction Sending

### What is Transaction Sending mode

Transaction Sending is a fast transaction sending mode provided by BlockRazor, aimed at users who have higher requirements for the speed of transaction inclusion, and is applicable to Solana, BSC, Robinhood Chain, Ethereum, and Base.

Compared to RPC, Transaction Sending focuses more on how to get transactions into the on-chain execution process more quickly after they are sent from the client. It leverages [BEF](/core-technology/blockchain-edge-fabric.md) to fully utilize the underlying mechanisms of different chains, providing a lower latency sending experience for the trading system.

### What users are suitable for Transaction Sending mode

* **Wallets / DEXs**: Team aiming to provide a faster sending experience for users worldwide.
* **Trading Bot / Quant Team:** Team with specific requirements for transaction inclusion speed and execution timing

### FAQ

<details>

<summary>What is the difference between Fast and RPC?</summary>

Both Fast and RPC are transaction sending capabilities, but they have different design goals.

RPC focuses more on transaction protection and general access capabilities. It provides standard JSON-RPC methods, focusing on addressing the MEV risks that transactions may encounter during public dissemination, and supports refund and disclosure policy configuration and customized RPC access, making it suitable for Wallets, DEXs, and project teams as a standard transaction sending entry point.

Fast prioritizes the speed of transaction on-chain processing. It optimizes the sending path through [BEF](/core-technology/blockchain-edge-fabric.md), helping transactions enter the on-chain execution process with lower latency. It is suitable for trading bots, quantitative strategies, and timing-sensitive trading scenarios that have higher requirements for on-chain timeliness.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blockrazor.io/transaction-submission/transaction-sending.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.