INTcoin Core v1.0.6 — chain healing release

INTcoin Core v1.0.6 — chain healing release

The LWMA difficulty-adjustment fix is shipped, the fleet is upgraded, and the chain stall at h=8614 is unblocked.

Downloads (verify against SHA256SUMS)

What’s fixed (4 IIPs landed Final)

  • IIP-0117 — Symmetric LWMA solvetime clamp. Burst-mining no longer pins difficulty up.
  • IIP-0118 — LWMA window 60 → 144. Single-event noise diluted.
  • IIP-0119 — Per-retarget damping ±30%. No more wild swings.
  • IIP-0120 — Emergency min-difficulty after 20×T stall. Chain liveness guaranteed.

Other v1.0.6 cleanups:

  • Legacy Kyber1024 KEM-name fallback removed (ML-KEM-1024 only)
  • I2P retry-storm fixed (per-destination exponential backoff)
  • .onion and .b32.i2p self-connection detection
  • intcoin_uptime_seconds Prometheus metric now correct
  • intcoin-cli --help lists all 4 networks (mainnet / testnet / signet / regtest)

Full changelog: https://gitlab.com/INT-devs/intcoin/-/blob/v1.0.6-stable/docs/user/CHANGELOG.md

:warning: This is a BREAKING release

v1.0.6 refuses connections from v1.0.3, v1.0.4, AND v1.0.5 peers. The protocol-version handshake bumps from 70003 → 70004. There is no soft-fork path, no flag-day height — every node must upgrade.

  • On v1.0.5 today → easy: download v1.0.6, swap binary, restart. Wallet, datadir, keys carry forward unchanged.
  • On v1.0.3 / v1.0.4 → upgrade directly to v1.0.6 — skip v1.0.5.

Linux source build (the canonical path)

Must rebuild on the host that runs it (RandomX bakes per-CPU features):

cd /path/to/intcoin
git fetch --tags && git checkout v1.0.6-stable
cmake -B build && cmake --build build -j$(nproc)
sudo cmake --install build
sudo systemctl restart intcoind intcoin-miner
intcoind --version    # should report 1.0.6

Windows users

Download intcoin-v1.0.6-stable-windows-x64.zip, right-click → Properties → Unblock (else SmartScreen flags), unzip, replace prior binaries, restart wallet.

:bar_chart: Live public chain dashboard

Public, auth-free, real-time:

https://intcoin.grafana.net/public-dashboards/30d0e9a455c447359a0f74d7ba3eece3

Shows: block height, network hashrate, peer count, difficulty, mempool — refreshed every 30 seconds with 24h history visible. Bookmark it; it’ll stay there. (Chain-level data only, no internal infrastructure exposed.)

Fleet status

UK, US, EU servers all upgraded and peering on protocol 70004. Community v1.0.6 nodes were already self-building from the GitLab tag within minutes of the release landing — appreciate everyone watching the releases page that closely.


Thanks for sticking with us through the stall. The bug → root cause → fix → release loop ran ~14 hours from “wait, why is difficulty still climbing?” to v1.0.6-stable on Releases. The lessons that one LWMA edge case taught us about behaviour at our specific hashrate scale will outlive this incident by a long way.

— INT-devs