bdnBlocks

bdnBlocks is a stream of all new blocks as they are propagated in the BDN. The blocks published in the bdnBlocks stream may include blocks that will not be accepted on chain. This stream offers significant performance speed over the newBlocks stream (from the Gateway or the node).

Service available on both Cloud-API and Gateway-API.

Stream Endpoint

  • Method: bdnBlocks

  • Cloud-API Endpoint: wss://<region>.eth.blxrbdn.com/ws

  • Gateway-API Endpoint: ws://127.0.0.1:28333/ws

  • Request type: gRPC,WSS

circle-info

Performance tip: If you don’t need parsed transaction fields, set parsedTxs: false to receive blocks ~20–60 ms faster with less overhead.

Parameters

Key

Description

Values

include

Fields to include in the block stream.

hash,header,transactions,uncles,future_validator_info,withdrawals

[Default: all] future_validator_info contains validator addresses for future blocks and indicates whether the validators are connected to the BDN (currently only supported in BSC) withdrawals

contains withdrawals for ETH block

parsedTxs

Controls whether transactions in each block are returned as fully parsed JSON objects (true) or as raw, unparsed RLP payloads (false). Disabling parsing reduces server work and improves delivery latency.

Type: boolean [Default: false]

Examples (Websocket)

Cloud-API

## ETH Example
wscat -c wss://virginia.eth.blxrbdn.com/ws --header "Authorization: <YOUR-AUTHORIZATION-HEADER>"
> {"jsonrpc": "2.0", "id": 1, "method": "subscribe", "params": ["bdnBlocks", {"include": ["hash"],  "parsedTxs": true}]}
< ......

Gateway-API

Response (Block Event)

circle-info

This response is for when parsedTxs is set to true in the stream subscription

Last updated