RPC Guide
Mazze exposes JSON-RPC over HTTP, WebSocket, and TCP. There are two RPC surfaces:
Mazze core (native) APIs.
EVM (Ethereum-compatible) APIs.
The exact set of enabled methods depends on your config.
Endpoints and configuration
All RPC ports and API allowlists live in run/hydra.toml.
Common fields:
jsonrpc_http_port,jsonrpc_ws_port,jsonrpc_tcp_port: Mazze core APIs.jsonrpc_local_http_port,jsonrpc_local_ws_port,jsonrpc_local_tcp_port: local-only Mazze endpoints (recommended for debug/admin calls).jsonrpc_http_eth_port,jsonrpc_ws_eth_port: EVM APIs.public_rpc_apis: core API allowlist (all,safe,mazze,debug,trace,txpool,test,pubsub, ...).public_evm_rpc_apis: EVM API allowlist (evm,eth,ethpubsub,ethdebug).
HTTP call examples
Mazze core status:
curl -s http://127.0.0.1:12539 \
-H 'content-type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"mazze_getStatus","params":[]}'Mazze call (latest_state):
EVM (eSpace) block number:
WebSocket pubsub example
Supply and burn calls
mazze_getSupplyInfo: returns chain supply aggregates from node state.mazze_getFeeBurnt: returns cumulative MIP-1559 burned amount.
Interpretation note:
Theoretical tokenomics maximum and live bridge liquidity are separate from direct RPC state values.
For current tokenomics model and bridge constraints, see:
../tokenomics/overview.mdand../tokenomics/bridge-liquidity.md.
Full RPC method list
Mazze core (native) APIs
Mazze filters
Mazze txpool
Mazze debug and admin
Mazze trace
Mazze test/dev
Mazze pubsub (WebSocket)
Methods:
Subscription kinds: newHeads, logs, newPendingTransactions, syncing, epochs.
EVM (Ethereum-compatible) APIs
Last updated