Skip to main content
Common questions about XOXNO infrastructure services.

​
General

MultiversX infrastructure: a Transaction Relayer for broadcasting and real-time data streaming, a DEX Aggregator for selected swap routing, and a Rust-native RPC Gateway.
No. All endpoints are public. Enterprise plans with higher limits are available on request.
XOXNO infrastructure is available on MultiversX mainnet (chain ID 1).
Enterprise customers receive SLA guarantees. Contact us on Telegram for details.

​
Transaction Relayer

Broadcast submits a transaction where the user pays gas. You sign the transaction and send it via the broadcast WebSocket action or POST /v1/broadcast. The relayer does not co-sign.Relay (Gasless V3) is an enterprise feature where the relayer pays gas for the user. You include a shard-matched relayer address in the transaction, sign it, and send it via the relay action. The relayer co-signs and broadcasts to the network.Most applications use broadcast. Relay requires enterprise access.
Relayer V3 lets you submit transactions where the relayer pays gas for the user. Include a relayer field in the transaction with the shard-matched relayer address, sign it, and send it via the WebSocket relay action. The relayer co-signs and broadcasts to the P2P network. This is an enterprise-only feature.
The sender’s shard must match the relayer’s shard. Use these addresses:
ShardRelayer address
0erd1l0x0n5yxsfcy93gm0vyvx9m9f7cte9h9vuq4am33ugpw3d5r3hvqx6f59h
1erd12yxd5phejzw83gn8qh6jfz6q9a0ekyyhkfd3c49r03mxw25l3a5swq3nf7
2erd13jxp0yjh7gjvzgrg5mj7e8rzhn5lzcye45l0p6e5996d543r7vrq9e50za
Compute the sender’s shard from their address and use the corresponding relayer.
The sender’s shard and the relayer address’s shard must match. Recalculate the sender’s shard and use the correct relayer address. See Relaying (Gasless V3) for details.
Each connection supports up to 64 topic subscriptions. The rate limit is 64 control messages per 5-second window. Maximum message size is 4 MB, and the heartbeat interval is 30 seconds (ping/pong). See Connection and limits.
Gas stats update within 50 ms when pending mempool transactions arrive or recent block averages change per shard, with a 5-second periodic refresh during idle periods. Data covers a 30-minute sliding window of 10-second buckets and includes per-shard min, max, average, and percentiles (p50, p75, p90) for both gas price and PPU.

​
DEX Aggregator

The aggregator analyzes liquidity across xExchange, AshSwap, JEX, and OneDex. Pool state updates in real time as on-chain changes occur.
For large trades, the aggregator splits the order across multiple paths to minimize price impact. You can control this with the maxSplits parameter (default 5). The algorithm parameter lets you choose between greedy, lagrangian, or hybrid split allocation strategies.
Yes. Pass the sender query parameter with your wallet address, and the response includes a complete transaction object ready for signing and submission.
A reverse quote lets you specify the desired output amount (amountOut) instead of the input amount. The aggregator calculates the required input, which is useful for “I want exactly X tokens” scenarios.
Quotes reflect pool state at the time of the request. Use the quote within a few seconds. Set a slippage tolerance (default 1%) to account for price movement between quoting and execution.

​
Gateway

Yes. The Gateway is a drop-in replacement for the standard MultiversX Go proxy. All endpoint paths, request formats, and response shapes are identical. Switch by changing the base URL to https://rust-gateway.xoxno.com. See the migration guide.
The Gateway routes each request to the correct shard observer by deriving the shard from the address (last byte of the public key modulo the number of shards). The Gateway handles shard resolution for you. See shard routing.
Block, hyperblock, heartbeat, validator statistics, and economics responses are TTL-cached. Account, transaction, and VM query endpoints return fresh data from the observer. The Gateway also deduplicates identical concurrent requests. See caching and deduplication.
Yes. Add blockNonce, blockHash, or onStartOfEpoch query parameters to most address and VM endpoints. The Gateway automatically routes historical queries to full-history observer nodes.
No. The Gateway forwards pre-signed transactions to observer nodes. You must sign transactions before submitting them via POST /transaction/send. For gasless transaction signing, use the Relayer.

​
Support

Join the XOXNO Telegram for technical support, feature requests, and community discussions. For enterprise inquiries, reach out directly to the team on Telegram.
Report issues on GitHub or in the XOXNO Telegram channel.