We stated in the previous blog post our intention to take a less ambitious protocol upgrade (Kekcoin Lore). However, we decided to judiciously review and audit the consensus critical code of our Kekcoin-segwit implementation first. This revealed to us the bug in the latest wallet release which caused the network to undergo a brief unintentional hard-fork. We found no further consensus mismatches between the original and SegWit clients which gives us confidence in our latest patch, Kekcoin-segwit v2.0.4. Upgrading a live distributed network is a difficult task and there may be further unforeseen issues, but we have experience in acting quickly to minimise the risk of unintentional forks and to date no negative consequences have arisen from these situations.
We are grateful for the patience demonstrated by you, our community, when dealing with wallet upgrades. We understand that you value transparency and so we will continue to announce publicly our intentions and to explain our development rationale.
We are pleased to announce that Kekcoin-segwit v2.0.4 is now available for download. The network is undergoing a backwards compatible yet mandatory soft-fork and it’s necessary for everyone to upgrade their wallet software, or risk being forced off the network. Please backup your wallet.dat files before updating as is standard practice when updating a wallet. No further action is required after updating the wallet software.
As a reminder, if you find any issues regarding your displayed balance compared to your expectations from the previous wallet, see these instructions from a previous blog post for a fix.
For power-users, we have a short tutorial on how to set up a new staking node for a Raspberry Pi.
Segregated Witness Activation: The deployment method for this soft-fork follows the generic mechanism described in BIP 9. The start time, after which stakers may signal they are aware of the up-coming soft-fork, is 1/1/2018. Soft-fork activation requires 70% of stakers to signal during an activation period of 10080 blocks (~1 week). Practically, the signalling is achieved by setting the nVersion field in a new block to a specific value. This “lock-in” period repeats every 10080 blocks until the required signaling threshold is attained or until 1/1/2019 is reached. If the threshold is reached then the soft-fork becomes active and any staking nodes who aren’t signaling will be forced off the network. If the threshold is not reached before the soft-fork time-out (1/1/2019) then the deployment will be considered failed.
Advantages of Kekcoin v2.0
As you may be aware, the Kekcoin code is based on Bitcoin-Core’s reference implementation. This upgrade takes Kekcoin from code-base v0.08 to v0.13, bundling roughly 3 years of development into one upgrade. A few notable changes are:
- Faster Synchronization (utilizing headers-first synchronization)
- Improved performance & security for signature functionality using libsecp256k1 instead of OpenSSL
- Block file pruning (Storage optimization)
- OP_RETURN output size increased to 80 bytes (Simplifying MemeChain implementation)
- Automatic use of Tor hidden services (if Tor is running)
- Hierarchical Deterministic Key Generation (Simpler address management for users)
- Segregated Witness (BIPs 141, 143, 144, 145) — see Update #7.
- Re-designed wallet GUI
To see a full, detailed list of notable changes pertaining to privacy, performance, security and general code modernization please see the Release Notes for Bitcoin-Core at https://bitcoin.org/en/version-history.
As well as numerous improvements to every aspect of the cryptocurrency, this upgrade better prepares the Kekcoin code-base for continual development and maintenance as the cryptocurrency space evolves.
The Kekcoin Team.