Live since block 53,000.
Blockle is merge-mined across ten algorithm lanes. Each lane used to set its own difficulty independently, which meant every lane earned the same share of blocks no matter how much real energy backed it — an ultra-efficient ASIC lane was rewarded the same as a power-hungry one. Block 53,000 changed that, and the rule has been in force ever since.
All lanes are now retargeted from one shared base difficulty, scaled per lane by a benchmark-measured energy-per-hash coefficient. Each lane must expend the same real power per block, so block production — and therefore reward and security weight — tracks actual energy draw rather than raw hashrate. Fork-choice work is energy-weighted too, so the heaviest chain is the one backed by the most power.
This is a mining-difficulty and fork-choice rule only. No address formats, keys, balances, supply, or transaction rules change.
This is already active. A node without this rule rejects post-fork blocks and is split off the network — if yours has not been upgraded, it is not following the main chain.
git pull
cargo build --release
# restart your node service, e.g.
systemctl restart blockle-node
Confirm the rule is present: blockle-cli getblockchaininfo should include
cross_algo_activation_height: 53000. Check you are on the live chain by
comparing your tip against the explorer.
Point your miner/pool at an upgraded node. getblocktemplate returns the
coupled difficulty bits automatically once you are on the new build — no pool config
maths required. Payout addresses are unchanged. Returns now follow your
share of real network power draw, not raw hashrate.
Nothing changed for your coins — addresses, keys and balances were unaffected. Just update to the latest Blockle wallet when prompted so you stay on the upgraded network. Get the latest wallet →
Coupling to measured energy-per-hash means reward and security both scale with the one thing an attacker actually has to spend — power. An efficient lane can no longer earn an outsized share or accumulate chain-work cheaply. The coefficients are fixed consensus constants derived from best-in-class hardware for each algorithm; the full methodology and the per-lane table are in the technical note below.
Technical note: docs/CROSS-ALGO-COUPLING.md. Live per-lane and global difficulty on the explorer.