Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/BlockRazorinc/docs_en/llms.txt

Use this file to discover all available pages before exploring further.

Algorithmic and quantitative trading systems are only as good as the data they run on. A stale world state means your model is pricing against outdated liquidity. A miscalibrated gas estimate means your order either fails to land or bleeds unnecessary cost. A missed on-chain signal means a position enters late. BlockRazor’s suite of high-performance data streams — Node Stream, Network Fee Stream, and Block Stream — addresses all three problems simultaneously, giving quant systems the real-time, low-latency data infrastructure they need to execute with precision.

​
Why quant and algo systems choose BlockRazor

Node Stream

Synchronise directly with a full node to keep your in-memory world state up to date with minimum latency — the foundation of any price or liquidity model.

Network Fee Stream

Receive real-time gas price, priority fee, and tip data derived from recent block history so your system always bids the right fee at the right moment.

Block Stream

Get low-latency pushes of confirmed block data to monitor signal transactions, track strategy positions, and trigger post-execution logic.

​
Core benefits

1

Synchronised world state via Node Stream

Node Stream gives your system low-latency, real-time synchronisation with a BlockRazor-managed full node. Rather than polling a public RPC and accepting unpredictable lag, your model subscribes to a continuous feed of account, slot, and state updates. This keeps your internal representation of pool reserves, oracle prices, and account balances current at all times — the prerequisite for accurate pricing and position management.
2

Dynamic gas optimisation via Network Fee Stream

Submitting transactions at the wrong gas price costs you in one of two ways: too low and your order misses the block; too high and you erode the profit margin of every trade. The Network Fee Stream pushes gas price, EIP-1559 base fee, priority fee, and Solana tip data in real time, calibrated against recent block history. Your execution layer can consume this feed directly and set fees adaptively rather than relying on static estimates.
3

Confirmed signal monitoring via Block Stream

Block Stream delivers low-latency block data the moment a block is confirmed. For a quant system, this is the trigger layer: detect that a hedging transaction has landed, confirm that a limit order filled, observe a large on-chain event that changes your model’s assumptions, or track the execution of a competing strategy. Block Stream provides this without the delay and variability of public node subscriptions.

​
Chain and service availability

StreamBSCEthereumSolanaBase
Node Stream✓———
Network Fee Stream✓—✓—
Block Stream✓——✓
BlockRazor offers bundle subscription plans for BSC-focused quant systems that combine Node Stream, Public Mempool, Block Stream, Fast Submit, and more into a single plan. See the pricing page for current options.

​
Integration patterns

Subscribe to the Node Stream WebSocket to receive real-time state updates from a BlockRazor full node. Use the provided enode endpoint to peer directly.
const ws = new WebSocket(
  "wss://stream.blockrazor.io/bsc/<api-key>/node-stream"
);

ws.on("message", (data) => {
  const update = JSON.parse(data);
  // Apply state delta to your internal world-state model
  worldState.apply(update);
});
Run Node Stream and Network Fee Stream together as a pair: Node Stream keeps your pricing model accurate, while Network Fee Stream ensures every order you submit arrives with a competitive fee. Together they eliminate the two most common sources of slippage in algorithmic execution.

Node Stream

Real-time full-node state synchronisation for accurate world-state modelling on BSC.

Network Fee Stream

Live gas price and priority fee data for adaptive fee setting on BSC and Solana.

Block Stream

Low-latency confirmed block data for signal monitoring and post-execution logic on BSC and Base.

Build docs developers (and LLMs) love

Get started for freeTalk to us