RobotBase Multi-Chain Data Agent

Ethereum node state from our own Reth (execution) + Lighthouse (consensus): sync state, height/head slot, peers, clients, and — while the node is still being provisioned — an explicit provisioning status. When to use: whether the ETH node is up/synced, or what stage its provisioning/sync is at. Do not use: for PoW hashrate questions — Ethereum is proof-of-stake (see pow_network_mining_intel).

Ethereum node state from our own Reth (execution) + Lighthouse (consensus): sync state, height/head slot, peers, clients, and — while the node is still being provisioned — an explicit provisioning status. When to use: whether the ETH node is up/synced, or what stage its provisioning/sync is at. Do not use: for PoW hashrate questions — Ethereum is proof-of-stake (see pow_network_mining_intel).

Monero node state: height vs target, sync flag, difficulty, txpool size, database size, monerod version and peer counts. When to use: whether the XMR node is synced and healthy, or how big its chain/txpool is. Do not use: p2pool/mining side → xmr_pool_status.

Our Monero p2pool (mini + nano sidechains) plus Monero network state: per-sidechain hashrate, miners, sidechain height/difficulty, blocks found, last block age, this node's workers, fee and the non-custodial flag. When to use: solo/p2pool mining economics on Monero, sidechain health, or which stratum endpoint to point a rig at. Do not use: plain node RPC state → xmr_node_status.

Kaspa node status: network height, DAA score, difficulty, network hashrate, DAG tips, block reward, 10 BPS cadence, next halving and the hashport ports this node serves. When to use: how high and how healthy the Kaspa node is, or the halving schedule. Do not use: our own pool's miners/blocks → kas_pool_status.

Kaspa chain-wide pool attribution computed locally: which pool found how many blocks, with percentage share, over a window of 1-720 hours, plus the newest attributed blocks. When to use: Kaspa mining decentralisation, competitor share, or checking how a pool performs. Powered by our own block index (hundreds of thousands of blocks attributed), not a third-party API.

RobotBase Kaspa solo hashport: tier state, pool hashrate, connected miners, accepted shares, blocks found, uptime, share difficulty, the last block found (hash, blue score, age) and stale/invalid counts. When to use: is the KAS hashport live, who is mining on it, did it ever find a real mainnet block. Do not use: chain-level hashrate → kas_node_status.

Ravencoin native assets straight from our ravend: pass an asset name or id for amount, units, reissuable flag and IPFS metadata, or omit it to list recent assets. When to use: token/asset checks on Ravencoin, where assets are UTXO-native rather than smart contracts.

Ravencoin node status: height, sync state, network hashrate, difficulty and client version. When to use: whether the RVN node is synced and how big the network is right now.

RobotBase Ravencoin solo hashport: engine state, pool hashrate, connected miners, shares, share difficulty, the Stratum endpoint, fee and the per-miner independent coinbase payout mode. When to use: is the RVN hashport open, is anyone mining, what endpoint do I point a GPU rig at. Do not use: node-level data → rvn_node_status.

Node status for DOGE or LTC (height, sync progress, peers, mempool tx count). When to use: Dogecoin or Litecoin node progress. For BTC/KAS/ZEC/RVN use chain_status (any chain in one call).

Halving countdown for every chain we run: height, next halving height, blocks remaining, ETA in days, and the reward before/after. When to use: an agent needs a precise schedule anchor (emissions, mining economics, long-horizon planning). Note: heights are read live from our own nodes, schedules are protocol constants. DOGE has no further halvings (flat subsidy).

Network hashrate and difficulty for BTC/KAS/ZEC/RVN/LTC/DOGE, with the method stated per chain (node-reported vs difficulty-derived). When to use: mining economics, security budget, or comparing chain weight. Do not use: pool-level stats → kas_pool_status / rvn_pool_status.

Look up one miner on our own hashports: hashrate, shares, stale/invalid, current difficulty and last-seen, by wallet address or worker name. When to use: a miner asks their agent "how is my rig doing on robotbase?". Privacy: the address is masked in the reply, and only an exact wallet/worker match returns data (no listings).

Ravencoin native assets straight from our ravend: pass an asset name or id for amount, units, reissuable flag and IPFS metadata, or omit it to list recent assets. When to use: token/asset checks on Ravencoin, where assets are UTXO-native rather than smart contracts.

Zcash coinbase attribution over the last 10-500 blocks: the shielded-pool share of block rewards (privacy mining), coinbase outputs split into consensus funding streams (lockbox) vs real miner payout addresses, and the pool tags miners printed into their own coinbase text plus our own /RobotBase/ tag. When to use: privacy-pool mining trends, shielded adoption, or checking whether our own pool found blocks. Scope: chain facts only — no third-party pool label list is applied.

All six Zcash value pools (transparent, sprout, sapling, orchard, ironwood, lockbox) with balances, share of supply and 1h/24h deltas. When to use: privacy-pool capital allocation, shielded-supply trends, ZEC macro flows. Do not use: node health → chain_status(zec).

Kaspa node status: network height, DAA score, difficulty, network hashrate, DAG tips, block reward, 10 BPS cadence, next halving and the hashport ports this node serves. When to use: how high and how healthy the Kaspa node is, or the halving schedule. Do not use: our own pool's miners/blocks → kas_pool_status.

RobotBase Kaspa solo hashport: tier state, pool hashrate, connected miners, accepted shares, blocks found, uptime, share difficulty, the last block found (hash, blue score, age) and stale/invalid counts. When to use: is the KAS hashport live, who is mining on it, did it ever find a real mainnet block. Do not use: chain-level hashrate → kas_node_status.

Ravencoin node status: height, sync state, network hashrate, difficulty and client version. When to use: whether the RVN node is synced and how big the network is right now.

RobotBase Ravencoin solo hashport: engine state, pool hashrate, connected miners, shares, share difficulty, the Stratum endpoint, fee and the per-miner independent coinbase payout mode. When to use: is the RVN hashport open, is anyone mining, what endpoint do I point a GPU rig at. Do not use: node-level data → rvn_node_status.

Monero fee estimate: per-byte rate, tiered rates (low/medium/high) and the quantization mask. When to use: how much fee an XMR transfer costs, or the current rate.

Latest Monero block header: height, hash, timestamp, difficulty, block reward, transaction count. When to use: XMR's most recent block time, latest height, or whether the chain stalled.

Monero mempool statistics: total bytes, total fees, and a transaction histogram grouped by size (congestion level). When to use: is XMR congested right now, or how many transactions are waiting.

Monero full-node info: height, sync state, difficulty, in/out connections, database size, mempool tx count, version. When to use: how high the XMR node is, whether it finished syncing, whether it is connected to the network.

Look up a Monero transaction by txid: still in the mempool or already mined, block height and confirmations, input/output counts, output indices. When to use: judge whether an XMR transaction or atomic swap is mined, or stuck unconfirmed past its timeout. Do not use: Bitcoin transactions → btc_tx_lookup.