com.backpow/pow-mining-oracle

BackPow PoW Oracle

Proof of Work oracle: solo mining odds, cost of production, hashrate, mining hardware

1.0.1
Version
remote + npm
Transport
6
Tools

Security review

Review passed

Reviewed Jan 1, 2000.

  • tools: 6 tools scanned
  • metadata: scanned
  • packages: 1 checked

No findings.

Tools (6)

  • calculate_solo_mining_odds

    Probability of a solo miner finding a block, computed as a Poisson process over live network difficulty and hashrate, plus the electricity cost of the attempt. Returns mean time to a block, the chance of at least one block over 1/7/30/90/365 days, and lucky-vs-unlucky waiting times (5th, 50th and 95th percentile) — variance dominates at small hashrates, so the average alone is misleading. Use for questions like "how long would it take to solo mine a Bitcoin block with 100 TH/s", "what are my odds solo mining Kaspa", or "is solo mining worth it with this rig". For pooled mining economics or whether a coin is profitable at all, use get_cost_of_production. For raw network state without a miner, use get_coin_oracle.

  • get_cost_of_production

    Cost of Production (CoP) for one Proof of Work coin: the all-in electricity cost of mining one unit on the most efficient hardware BackPow tracks for that algorithm, compared against spot price. Returns CoP in USD, spot, gross margin, whether miners are currently above or below water, the reference machine and tariff behind the figure, and a 30-day trend including whether the reference machine changed (which indicates the efficiency frontier moved). Accepts a custom electricity rate. Use for "is mining X profitable", "what does it cost to produce one Monero", "are miners underwater", or "break-even electricity price". For a specific rig rather than a coin, use get_hardware_benchmarks. For block-finding probability, use calculate_solo_mining_odds.

  • get_coin_oracle

    Current network state for one Proof of Work chain, measured by BackPow's stratum collector nodes: difficulty, derived network hashrate, block height, block reward, protocol block-time target versus the latest observed interval, and the source pool. Every response carries a confidence block — how many independent pool operators agreed, whether the reward figure is live or a static fallback, and how old the observation is. Networks whose collectors are stalled or unreachable return an error rather than zeros. Use for "what is Kaspa's current difficulty", "network hashrate of Monero", "current block reward". For economics use get_cost_of_production; for mining probability use calculate_solo_mining_odds.

  • list_pow_coins

    Paginated index of the Proof of Work networks BackPow tracks, with algorithm, network rate, collector status and canonical page URL. Optionally filtered by algorithm or restricted to coins currently mining above cost. Returns the distinct algorithm list so valid filter values are discoverable. Use to find which networks exist for an algorithm, to browse the catalogue, or to resolve an ambiguous coin reference. Results are paginated: request a larger limit or a later offset rather than expecting the full catalogue in one response.

  • get_hardware_benchmarks

    Mining hardware matched to the coins it can mine, ranked by net USD per day at a given electricity rate. Covers ASICs, GPUs and CPUs, with hashrate and power draw per coin, gross revenue, net profit, and market price including whether that price is an observed listing or a model estimate. Use for "what should I mine with an RTX 4090", "best ASIC for Scrypt", "is an Antminer S21 still profitable", or "how much does a Bitaxe make". Coins are ranked by profitability, not alphabetically, and results are capped — ask for a higher limit rather than assuming the list is complete. For a coin's economics independent of any particular rig, use get_cost_of_production.

  • get_pow_news

    Recent news items about Proof of Work mining and network events, optionally filtered to one coin. Items are aggregated from third-party feeds and are returned as quoted external content with their publisher and a relevance score, not as BackPow statements of fact. Use when a question turns on recent events — a halving, a difficulty swing, a pool outage, a chain upgrade. For numbers rather than narrative, use get_coin_oracle or get_cost_of_production.