> 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/get-started/about-blockrazor.md).

# About BlockRazor

BlockRazor is a research institution focused on Web3 infrastructure and DeFi trading. It focuses on solving key problems in trading scenarios and continuously transforms its [research results](https://blockrazor.io/blog/) into infrastructure products and services, creating a globally distributed, high-performance multi-chain infrastructure system for builders who pursue excellence.

Through long-term research and engineering practice, BlockRazor provides integrated capabilities covering Transaction Submission, Streams, and Block Builder for Wallets, DEXs, Trading Bots, Searchers, and quantitative trading systems, helping customers obtain faster block transaction signals and better transaction execution results on Ethereum, BSC, Solana, and Base.

### Transaction Submission

BlockRazor offers multiple transaction submission modes to adapt to the different needs of various businesses in terms of mev protection, inclusion speed, and transaction costs:

* [RPC](/transaction-submission/rpc/overview.md): Provides standard JSON-RPC methods, offers MEV protection for transactions, and supports real-time rebates.
* [Block Builder](/transaction-submission/block-builder/overview.md): A block building service for BSC, providing users with a high-win-rate block building commitment and low-latency access capabilities.
* [Fast](/transaction-submission/fast/overview.md): Utilizes [BEF](/core-technology/blockchain-edge-fabric.md) to improve inclusion speed, suitable for users with extremely high requirements for transaction speed.
* [Gas Sponsor](/transaction-submission/gas-sponsor.md): Provides gas sponsorship for users whose native tokens are insufficient to cover transaction fees, enhancing the user trading experience.

### Streams

BlockRazor offers a variety of high-performance real-time data streaming capabilities, helping trading systems and infrastructure systems obtain signals earlier and synchronize states faster:

* [Mempool](/streams/mempool.md): Low-latency data streams for mempool pending transactions, enabling real-time monitoring of trading signals in various scenarios such as backrun, copy trading, and sniping.
* [Block Stream](/streams/block-stream.md): Provides low-latency streams of the latest blocks and confirmed transactions, and is used to monitor confirmation signals, block events, and on-chain results.
* [Node Stream](/streams/node-stream.md): Helps users synchronize the latest blocks and world state with their own full nodes with lower latency, making it suitable as a low-level input capability for systems that rely on local state.
* [Network Fee Stream](/streams/network-fee-stream.md): Provides real-time Gas Price, Priority Fee, or Tip data based on recent historical block data, which can be used to optimize transaction parameters and sending strategies.


---

# 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/get-started/about-blockrazor.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.