Docs
Docs
Home
Getting Started
Agent Tooling
CLI
Supported Chains
Acala
Aptos
Arbitrum
Arc
Asset Hub
Astar
Avalanche
Base
Berachain
Bifrost
Binance Smart Chain
Bittensor
Blast
Boba Network
Bridge Hub
Celo
Centrifuge
Chiliz
Cronos
Enjin
Ethereum
Etherlink
Flow EVM Gateway
Gnosis
Hydration
Hyperliquid
Immutable
Ink
IoTeX
Kusama
Linea
LISK
Manta Atlantic
Manta Pacific
Mantle
MegaETH
Monad
Movement
Neuroweb
opBNB
Optimism
Plasma
Polkadot
Polygon
Pulsechain
Robinhood
Ronin
Scroll
Sonic
Starknet
Taiko
Tempo
Sui
TRON
Unichain
Viction
World Chain
XDC Network
XX Network
Zetachain
zkSync Era
Zora
Supported ChainsPlasmaJSON-RPC APIMining Methods

eth_hashrate - Plasma RPC Method

Get the legacy eth_hashrate compatibility value on Plasma. Public endpoints may return `0x0` or an unsupported-method error depending on the client.

Plasma RPC endpoint: endpoint URLs, plans and pricing.

Returns the legacy eth_hashrate compatibility value on Plasma. Depending on the client behind the endpoint, this call may return a hex quantity like 0x0 or a method-not-found style error.

Why Plasma? Build on an EVM Layer 1 for stablecoin payments with PlasmaBFT consensus and Reth execution with 1 second blocks, XPL gas, full EVM JSON-RPC, and debug plus txpool on Dwellir.

Note: Treat eth_hashrate as a node-local mining metric and compatibility value. Public endpoints often report 0x0 or reject the method entirely, so it is not a reliable chain-health or consensus signal.

When to Use This Method

eth_hashrate is relevant for payment app developers, wallet teams, and teams shipping Solidity contracts for dollar transfers:

  • Node Diagnostics - Check whether the connected client reports a legacy hashrate metric
  • Client Capability Checks - Distinguish between 0x0, unsupported-method, and method-not-found responses
  • Dashboard Integration - Display the metric alongside other node status data when it is available

Best Practices

  • Returns 0x0 on proof-of-stake chains (post-Merge) and most modern deployments
  • Not relevant for most production environments; treat as informational only
  • Do not rely on this method for chain health or consensus signals
  • Use eth_syncing or eth_blockNumber for reliable node status monitoring
JSON-RPC request
{
  "jsonrpc": "2.0",
  "method": "eth_hashrate",
  "params": [],
  "id": 1
}

Code Examples

Common Use Cases

1. Compatibility-Aware Status Dashboard

Display the reported compatibility value alongside other client status signals without assuming the method is always available:

JavaScript
async function getMiningStats(provider) {
  const blockNumber = await provider.getBlockNumber();
  let hashrate = null;
  let supported = true;

  try {
    hashrate = await provider.send('eth_hashrate', []);
  } catch (error) {
    supported = false;
  }

  return {
    supported,
    hashrate: hashrate ? parseInt(hashrate, 16) : null,
    currentBlock: blockNumber
  };
}

2. Capability Check

Check whether the connected client reports eth_hashrate at all:

JavaScript
async function getHashrateStatus(provider) {
  try {
    const hashrate = await provider.send('eth_hashrate', []);
    return { supported: true, raw: hashrate, isZero: hashrate === '0x0' };
  } catch (error) {
    return { supported: false, message: error.message };
  }
}

console.log(await getHashrateStatus(provider));

Error Handling

Common errors and solutions:

Error CodeDescriptionSolution
-32603Internal errorNode may be initializing - retry after delay
-32601Method not foundNode client may not support this method
-32005Rate limit exceededReduce polling frequency

Related Methods

  • eth_mining - Check if the node is actively mining
  • eth_coinbase - Get the mining/coinbase address
  • eth_blockNumber - Get the current block height

txpool_content

Inspect the full pending and queued transaction pool on Plasma. Useful for mempool analytics, transaction replacement debugging, and operational monitoring.

Polkadot RPC Documentation

Complete JSON-RPC API documentation for Polkadot blockchain integration. Learn how to interact with Polkadot nodes using WebSocket and HTTPS endpoints.

On this page

When to Use This MethodBest PracticesCode ExamplesCommon Use Cases1. Compatibility-Aware Status Dashboard2. Capability CheckError HandlingRelated Methods