Skip to main content
Four independently deployable surfaces cover the full MultiversX lifecycle: chain observation, swap routing, transaction broadcasting, and node operation. The first three share an event-driven backbone; mxnode is operator tooling installed on each validator or observer host.

Core services

Service endpoints

Data flow

Path 1: Gas and block observation

The Relayer participates as an observer in the P2P gossipsub network, extracting gas prices from pending mempool transactions and recently finalized blocks. Per-shard gas statistics reach clients within 50 ms of new mempool activity; network snapshots follow at adaptive intervals tuned to block time.

Path 2: Account and transaction updates

The notifier ingests finalized events and forwards them to the Relayer: balance mutations, nonce increments, and transaction confirmations. The Relayer then distributes each update to every client subscribed to the relevant address or transaction hash.

Path 3: DEX aggregation

The Aggregator receives pool state changes from the notifier the moment they finalize on-chain. On each quote request, it evaluates liquidity across all supported DEXs, computes the split route, and returns a ready-to-sign transaction.

Path 4: Chain state queries

The Gateway forwards HTTP requests to shard observer nodes. It derives the target shard from the request (usually the address), selects an observer via round-robin, and returns the response. The Gateway TTL-caches block, hyperblock, and validator data; it coalesces identical concurrent requests into a single observer call.

When to use which service

Combine the Gateway with the Relayer when you need both reads and events: use the Gateway for on-demand chain queries and the Relayer WebSocket for gas stats, account deltas, and transaction confirmations.

Internal components