Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_mining_difficulty_adjustment

Calculate projected Bitcoin mining difficulty adjustments, next difficulty target, remaining retarget time, and hash rate momentum from epoch progress and average block time.

Instructions

Bitcoin Mining Difficulty Adjustment & Block Time Estimator. Calculate upcoming Bitcoin epoch difficulty adjustment percentage, estimated hash rate change, and average block discovery interval. Discipline: CRYPTO. Governing mathematical model / formula: New Difficulty = Old Difficulty × (Actual 2,016 Block Duration in seconds / 1,209,600 target seconds).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of projected_difficulty_adj_pct (Projected Difficulty Adjustment), next_difficulty_target (Projected Next Difficulty), remaining_epoch_days (Time Remaining Until Retarget), network_hashrate_growth (Implied Hashrate Momentum) using current_difficulty_trillion (Current Network Difficulty (Trillion) in T), blocks_elapsed_in_epoch (Blocks Mined in Current Epoch in blocks (of 2,016)), average_block_time_sec (Measured Average Block Time (Seconds) in seconds). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Bitcoin Mining Difficulty Adjustment & Block Time Estimator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "mining-difficulty-adjustment"

    • category (string): "crypto"

    • name (string): "Bitcoin Mining Difficulty Adjustment & Block Time Estimator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.projected_difficulty_adj_pct (Projected Difficulty Adjustment): Formatted display string (e.g. '+6.19% Increase')

      • metrics.next_difficulty_target (Projected Next Difficulty): Formatted display string (e.g. '89.7 T')

      • metrics.remaining_epoch_days (Time Remaining Until Retarget): Formatted display string (e.g. '3.7 Days')

      • metrics.network_hashrate_growth (Implied Hashrate Momentum): Formatted display string (e.g. 'Hashrate Expanding Faster than Target')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_mining_difficulty_adjustment"
  }
}

Input Schema

NameRequiredDescriptionDefault
average_block_time_secNoMeasured Average Block Time (Seconds) (seconds). Target is exactly 600 seconds (10 minutes). Default: 565. Min: 300. Max: 900.
blocks_elapsed_in_epochNoBlocks Mined in Current Epoch (blocks (of 2,016)). Progress through 2,016-block difficulty period. Default: 1450. Min: 100. Max: 2015.
current_difficulty_trillionNoCurrent Network Difficulty (Trillion) (T). Current epoch target difficulty (T = 10¹²). Default: 84.5. Min: 10. Max: 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

Score is being calculated.

Deploy Server

Other Tools