New release: Freicoin v12.1.2-10135

[Mark Friedenbach 92]

Freicoin version 12.1.2-10135 is now available from:

•  Linux 32-bit
•  Linux 64-bit
•  macOS (app)
•  macOS (server)
•  Windows 32-bit (installer)
•  Windows 32-bit (zip)
•  Windows 64-bit (installer)
•  Windows 64-bit (zip)
•  Source

This is a new point release, enabling soft-fork deployment of a collection of time-lock related protocol features.

Please report bugs using the issue tracker at github:

  https://github.com/tradecraftio/tradecraft/issues

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/Freicoin-Qt (on Mac) or freicoind/freicoin-qt (on Linux).

Downgrade to a version < v12

Because release v12 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with pre-v12 versions of Freicoin or other software.

If you want to downgrade after you have done a reindex with v12 or later, you will need to reindex when you first start Freicoin version v11 or earlier.

This does not affect wallet forward or backward compatibility.

Notable changes

First version bits BIP9 softfork deployment

This release includes a soft fork deployment to enforce BIP68 and BIP113 using the BIP9 deployment mechanism.

The deployment sets the block version number to 0x30000001 between midnight 16 April 2019 and midnight 2 October 2019 to signal readiness for deployment. The version number consists of 0x30000000 to indicate version bits together with setting bit 0 to indicate support for this combined deployment, shown as "locktime" in the `getblockchaininfo` RPC call.

(The leading bits to indicate version bits is actually 0x20000000, but version bits MUST be indicated and bit 28 set during this time period due to the earlier deployment of the coinbase-MTP soft-fork.)

For more information about the soft forking change, please see:

    https://github.com/bitcoin/bitcoin/pull/7648

This specific backport pull-request to v0.12.1 of bitcoin, which this release is based off of, can be viewed at:

    https://github.com/bitcoin/bitcoin/pull/7543

Unlike bitcoin, this soft-fork deployment does NOT include support for BIP112, which provides the CHECKSEQUENCEVERIFY opcode. Support for checking sequence locks in script will be added as part of the script overhaul in segwit, scheduled for deployment with Freicoin v13.

For more information regarding these soft-forks, and the implications for miners and users, please see the release notes accompanying v12.1-10123.

[BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki
[BIP65]: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki
[BIP68]: https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki
[BIP112]: https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki
[BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki

12.1.2-10135 Change log

• `26c3508b` [Chainparams]
  Add recent checkpoint, block #250992.
   
• `989cc70c` [Consensus]
  Add activation logic for BIP68 and BIP113.

Credits

Thanks to who contributed to this release, including:

• Mark Friedenbach

As well as everyone that helped translating on Transifex.
 

[Skaro 129]

I'm not the greatest coder but if you have a math or numerical methods  problem I could help.

 

 

[Mark Friedenbach 92]

Skaro, maybe you could help out on the following issue, a blocker for deploying forward blocks?

https://github.com/tradecraftio/tradecraft/issues/3

If so, I could provide a bit more detail about my current thinking in regards to that.

[Skaro 129]

Hi Mark. That sounds interesting.

But first of all, I understand the link you sent me: "Investigate replacing difficulty adjustment algorithm". I'm not sure I understand what you wrote:   "a blocker for deploying forward blocks". Are they talking about the same thing?

 

 

[Mark Friedenbach 92]

Yes it is a blocker for forward blocks (meaning: forward blocks depends on this being finished) because the difficulty adjustment algorithm can only be changed as a soft-fork simultaneously with deployment of forward blocks.

[Skaro 129]

Ok.

You said that "It has been demonstrated that this only works for the dominant coin of a proof-of-work system". Do you have a reference to this?

 

[Mark Friedenbach 92]

I don't know if there's a paper or anything looking at that. It is more a statement of our experience competing with other SHA-256 coins, and the bitcoin cash ecosystem experiencing exactly the same thing a number of years later.

This sort of discussion should probably happen on the GitHub issue.