@reddink reddink released this Jan 27, 2018 · 5 commits to master since this release

Assets 9

Reddcoin Core

Reddcoin Core v is available with the following updates:

  • additional dnsseed nodes across global locations (Europe, US, Asia)
  • resolve some compiler issues
  • fix some gitian build issues
  • Update debian installation instructions
  • improve layout of QT splash screen
  • typographical fixes
Jan 20, 2018
build: Bump version, update release notes, update copyright year
Dec 23, 2017
Bump version
Add release notes

@reddink reddink released this Aug 12, 2016 · 33 commits to master since this release

Assets 9

Reddcoin Core 2.0.0

Version 2.0.0 is the official release version of Reddcoin Core. On top of the new features, this update contains very important security fixes and all users MUST upgrade to this version as soon as possible. Details on several vulnerabilities were made public by the Bitcoin team (Official Bitcoin warning) regarding the issues. It is particularly important that users who are staking do upgrade, as once BIP 66 is enforced, version 3 blocks will be rejected from the network entirely.

Reddcoin 2.0.0 is a complete rebuild based off Bitcoin 0.9. This means in terms of the code-base we introduced all the changes up to Bitcoin 0.9.5 into this version of Reddcoin Core.

We have also included a couple of features from the 0.10 build including a connected peers tab and bandwidth monitoring

We therefore suggest to read the release notes of Bitcoin up to and including 0.9.

v2.0.0 is a recommended update for all users.

Notable changes

For further explanation of these, see the above mentioned Bitcoin release notes.

Code-base switched to Bitcoin

In efforts to improve the fast adoption of upstream changes, Reddcoin was switched from using litecoin to bitcoin code base.

New utility applications

Reddcoin-cli for RPC command line functionality. Moving to split the client and server components from reddcoind

Faster synchronization

Reddcoin Core 2.0.0 includes parallel block synchronization to greatly reduce the initial blockchain synchronization time.

Strict signature encoding (BIP66)

This release activates BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (4). These rules will only activate once a certain number of blocks are mined with this new version. It will take effect after 85% of the network (6120/7200 blocks) are generating v4 blocks (7200 blocks is equivilant to 5 days worth of blocks).

NOTE: This is not a hard fork, as all existing wallets will accept version 4 blocks, although they'll fail to enforce the new requirements.


Once the above rule is activated, the network will reject the creation of version (3) blocks (stakes on earlier clients e.g v1.4.1). Transactions using earlier clients will be accepted by the network

RPC access changes

RPC access now supports binary network addresses. This means that you can specify a single IP address, a CIDR network address or a netmask for accessing the RPC service. Please note, wildcard string matching no longer works and will display an error in the debug.log file when you attempt to use use a wildcard string in the rpcallowip= variable, either as a config setting or launch parameter.

Before After
rpcallowip= rpcallowip=
rpcallowip=10.0.0.* rpcallowip=
rpcallowip=10.0.* rpcallowip=
rpcallowip=* rpcallowip=::/0
rpcallowip=192.168.1.* rpcallowip=

Note: IPv6 addresses can also be used.

Stakeminer will wait for both the blockchain and network

This release will allow the staking of wallets that are not encrypted. Previously, if a wallet was not encrypted, the wallet would attempt to stake blocks as they were being downloaded. The wallet will now wait before staking is enabled.

It is however highly recommended to encrypt your wallet for your own peace of mind.

QT Debug window includes network and peer details

An addition to the QT wallet is the network graph tab to visually monitor network usage and the peers details tab to display other attached nodes.

DNS Seeds added

Additional dns seeds (dnsseed.redd.ink/testnet-dnsseed.redd.ink) for main and testnet to create some resilience for the network discovery

General comments

Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Reddcoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Reddcoin Core completely before you make a copy of your wallet.dat.


c349881b9ea4496cac3f348647317d1b585306fbdfff57bb4fa2687cf0148bfb *reddcoin-
f34eb8f1929d0b10d400834cf89e2db417060e5e7437e20e3557fda685614f9c *reddcoin-
547c647fc61772288f282dda021861dc11b902b780915f4cb7ccb4878f260808 *reddcoin-
e515ff56e675c3d60b4203feedb387a1a906a0171977ed25c5294cf4563f4a22 *reddcoin-2.0.0-win32-setup.exe
e2e15bc05d3460a6f1d1132db492540318dd343136ceb3e89986eae8edd1fa3c *reddcoin-2.0.0-win64-setup.exe
dfce44c9ae1d6a6cd3a7f1ac8f0730a427b7b2162f94f2bac177cb027c5628c8 *bootstrap.dat.xz

@laudney laudney released this Jan 12, 2015 · 5245 commits to master since this release

Assets 6
  • Update IP addresses of official nodes
  • Use consistent timestamp rules for coinstake transactions and blocks.
Assets 6
  • Change wording for staking info
  • Update staking-related RPC calls
  • Fix a bug that causes a staking wallet to crash upon exit
  • First official release of Social Wallet

@laudney laudney released this Aug 2, 2014 · 5285 commits to master since this release

Assets 5
  • Fix bug of timestamp for old transactions in orphaned blocks.
  • SHA256 checksums below are signed by laudney's PGP key:

Hash: SHA512

85be83a644e19b4683015d49590e73b99c17e8a7403acb52347dab0509c2740a reddcoin-
3843eb36dd7da30fe4bd7abfb9bad05bbd40ad124e1062964bb0203be24a53e1 reddcoin-
9b87b1f87b40fcaa67e0b5be25a95639fdf005b2838c01597d9d4c99f3fe00dd reddcoin-
Comment: GPGTools - https://gpgtools.org


Assets 2
  • Implementation of PoSV
  • PoSV starts at block 260,800 which is expected to be minted around 7pm GMT on 2nd August, 2014
  • Mandatory upgrade for everyone except mining pools.
  • Mining pools must run daemons v1.2.1.0 to generate new PoW blocks which are accepted into the blockchain.