Releases: madross/incakoin-new
v.1.5.2.0 release
v.1.5.1.0 client fixes
fixed client issue of 0 connections on new wallets with updated node ip
client now generates its own incakoin.conf file for those struggling to get one setup
v1.5.0.0 IncaKoin 2017 Protocol Update
Protocol Activation Time: 1505075400 UTC time - (GMT): Sunday, September 10, 2017 8:30:00 PM
Change Log:
- New checkpoint server public key
- checkpoints.cpp now expects WIF for checkpoint private key
- Internal wallet stake weight calculation is increased by 100 times. This will make stakes have a much higher chance of staking, and allow the PoS difficulty to not be pegged to the lower block
- Block maturity is changed to 1000 blocks
- Maximum reorganization depth is 50 blocks. Blocks deeper than 50 will not be seen as a valid entry point for reorganizing the blockchain.
- Chain trust score calculation for PoW blocks will no longer be a score of 1. They will instead be a similar calculation to PoS trust score, but with decreasing score for each PoW block tha$
- PoW block reward is changed to 100 coins.
v1.4.1.0
RECOMMENDED UPDATE v1.4.1.0
IncaKoin version 1.4.1.0 is now available from:
https://github.com/madross/incakoin-new/releases/
This is a bugfix release version who's primary purpose is to address
the issues with post-fork PoS block generation.
The hard-fork changed PoS rules from 100% every 90 days to 9% every 35 days,
however the code changes previously submitted failed to implement this change fully.
While the network would indeed accept a PoS block with an input age of 35+ days,
the client itself would refuse to generate a PoS block unless the input age was 90+
days.
This release includes a fix to such behavior, resulting in the client successfully
generating PoS blocks with inputs that are at least 35 days old.
Upgrading and downgrading
How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/IncaKoin-Qt (on Mac) or
IncaKoind/IncaKoin-qt (on Linux).
Downgrade warning
Downgrading from this version to v1.4.0.0 is technically possible, simply replace
the binaries from this version with the previous version's binaries. However,
downgraded clients will not benefit from the PoS block generation fixes and
will once again be in a situation where the client will require inputs that are
at least 90 days old before generating a PoS block.
Note for self-compilers
IncaKoin releases for Windows/OSX/Linux are compiled against Berkeley DB
version 4.8.30, while the Raspberry Pi 2 releases are compiled against Berkeley
DB version 5.3.28.
If you have previously self-compiled IncaKoin, you can use the release binaries
provided here ONLY if your previously self-compiled binaries were compiled
against a matching (or newer) version of Berkeley DB.
Berkeley DB versions are not interchangable with each other in a traditional
sense. Older version files are "upgraded" to newer version files automatically
when opened with a newer version, thus breaking any and all backwards
compatibility with older versions of Berkeley DB.
eg. if you self-compiled previously using Berkeley DB v5.3.28+, You will
NOT be able to use the release binaries provided here (unless your target
happened to be a raspberry pi)
Notable changes since 1.4.0.0
Client-side PoS Block Generation Fix
Clients will no longer adhere to the old network requirements of needing
inputs that are 90+ days old. Instead, the client will adopt the new network
standards and use inputs that are 35+ days old.
This is a non-forking change as the issue was not with network acceptance,
but rather client-side block generation. As such, this release is not technically
a "Mandatory" release, but is recommended for anyone who wishes to participate
in staking.
Strict versioning and pre-release support
The build system has been updated to support the use of pre-release versions
as well as tagged versions. This is a security related update that formats the
client's version string based on the repository status. The particular structure
is as follows:
- If the local source tree is consistent with a git tag, then the tag name is used as
the version string. - If the local source tree is consistent with a git commit, then the commit's short
hash is appended to the version string. - if any files have been modified, then the
-dirty
suffix is appended to the version
string.
This will hopefully help in identifying wither or not a particular build is indeed using
the official release repository, or if modifications have been made.
Correction of the Coin's Unit Name
The previous release(s) had an incorrect unit name associated with the GUI wallet.
The string "INCA" was appearing in various places that should have read "NKA"
v1.4.1.0 Changelog
- [f2d165e] Version 1.4.1.0 Release
- [3b076dd] [Qt] Add a timer to update the staking icon and weights
- [126bb36] Remove unnecessary or improperly formatted whitespace
- [d644c98] Update .gitignore file
- [1d8bd90] Show warning when running a non-release version
- [01f5dca] Update build files (makefiles/pro)
- [f15302c] Ensure the empty obj path is included
- [be83dad] Update Win/Mac deployment scripts
- [e4a6ca4] Update genbuild.sh and version macros
- [f6a3d9d] Fix more instances of "INCA" being used instead of "NKA"
- [5c03f53] Remove ignored defaultcodec tag from translation sources
- [5adb0ec] Remove generated Qt translation binary files
- [2664533] Correct port numbers listed in help
- [3fd45e1] Remove arbitrary constants for ports
- [78c6b4a] Correct the unit name back to "NKA"
- [11f4784] Use correct fork time for client version disconnects
- [25fca70] Fix staking minimum age detection