Korsh Core v0.0.5 — consensus fix + new GUI

Korsh Core v0.0.5

Consensus fix — update before block 14000.

What's new

Consensus split fixed (issue #1)

A masternode registration still using the old pre-rebrand port (:8383) could split the network:
nodes running the original v0.0.2 binaries rejected it while v0.0.3/v0.0.4 accepted it, producing
orphaned blocks. v0.0.5 gates the legacy port (and the legacy message-magic signatures) to the
historical chain (blocks <= 3515), so every node agrees on the rules for new blocks.

• New ProRegTx/ProUpServTx with :8383 are rejected (bad-protx-netinfo-port)
• Legacy message-magic signatures are rejected (bad-protx-sig)
• Historical sync (blocks <= 3515) still accepts both, so fresh nodes sync the whole chain
• If your masternode registration used :8383, re-register with :9777

Fresh GUI

The desktop wallet includes the full v0.0.5 redesign.

Sporks permanently disabled on mainnet

All mainnet sporks stay hardened to 2099 (same behavior as v0.0.4) — there is no activation height, no signer-key override and no spork governance on Korsh mainnet. The v0.0.5 retarget/spork upgrade is set to height 999999999 and never activates; the only scheduled activation remains V19 (the masternode wizard fix) at block 14000. PoW, rewards, masternode collateral, UTXO validation and chain selection are not gated by spork keys.

Everything from v0.0.4

• Masternode database self-healing on every startup (reorg / restart-loop fix)
• No reindex needed

Upgrading

Block 14000 (~Oct 1, 2026) activates the V19 network upgrade (wizard) — update before that block.

IMPORTANT: do NOT start your node with -reindex-chainstate. 0.0.5 self-repairs on a normal start.

Assets

• korsh-0.0.5-macos-arm64.tar.gz — macOS (Apple Silicon)
• korsh-0.0.5-win64.zip — Windows x64
• korsh-0.0.5-linux-x86_64.tar.gz — Linux x86_64
• SHA256SUMS.txt — verify your download