For AI agents: an LLM-friendly Markdown version of every page is available by appending .md to its URL or by sending an Accept: text/markdown request header. The full documentation index is at https://www.ankr.com/docs/llms.txt
Skip to main content

Redbelly


Redbelly API is available on Web3 API platform.

Redbelly Network is a Layer 1 blockchain for tokenized real-world assets. It pairs an EVM execution layer with DBFT (Democratic Byzantine Fault Tolerance) consensus, which is leaderless and tolerates fewer than n/3 Byzantine nodes: transactions reach deterministic finality in seconds and the chain cannot fork. A super-block optimization commits proposals from all governor nodes together instead of one leader's block at a time. Accounts are tied to verifiable credentials, so regulated issuers can settle structured products on a public network.

In order for your Web3 application to interact with Redbelly — either by reading blockchain data or sending transactions to the network — it must connect to a Redbelly node. Developers interact with the blockchain using the methods provided by the API.

The API interaction follows the JSON-RPC which is a stateless, light-weight remote procedure call (RPC) protocol. It defines several data structures and the rules around their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over HTTP, or in other message-passing environments. It uses JSON (RFC 4627) as data format.


Methods supported


Not available on Redbelly:

The Redbelly node exposes the eth, rbn, rpc, txpool, and web3 modules only, so there is no debug_* and no trace_* on any service plan. net_version and net_listening are not implemented either, unlike on other EVM chains. See Unsupported methods for the full list.


Methods

web3, eth