Skip to content

Releases: gridcoin-community/Gridcoin-Research

5.4.9.0-leisure

16 Feb 00:59
5.4.9.0
9042f39
Compare
Choose a tag to compare

[5.4.9.0], 2025-02-16, leisure

This is a maintenance leisure release and is probably the last leisure release before the
upcoming Natasha milestone mandatory release. The changes here are largely behind the scenes
bug fixes and adjustments to the build process to ensure compatibility with newer distributions.

Enjoy.

Jim Owens

P.S. the Windows, MacOS, and Debian builds are found here on the release page. Other builds are done by the maintainers for the various distributions.

Added

  • depends: add cross arm64-darwin support #2775 (@div72)
  • build: add missing randomness checks #2772 (@div72)
  • init, registry: Support -clearallregistryhistory startup parameter #2773 (@jamescowens)

Changed

Removed

  • refactor, misc: remove CBitcoin(Address|Secret) #2634 (@div72)

Fixed

5.4.9.0-testnet

19 Feb 22:13
9042f39
Compare
Choose a tag to compare
5.4.9.0-testnet Pre-release
Pre-release

This is simply a placeholder to hold testnet packages that use a different executable name for testnet. It is otherwise identical to the 5.4.9.0 production release.

5.4.8.4-testnet

28 Jan 16:12
c9f3674
Compare
Choose a tag to compare
5.4.8.4-testnet Pre-release
Pre-release

Testnet release of 5.4.8.4 for testing. This is RC2 for 5.4.9.0 maintenance release as part of the Natasha milestone.

This is for testnet network only unless permission is granted to use on mainnet by a core dev.

5.4.8.3-testnet

02 Nov 23:10
7b3748b
Compare
Choose a tag to compare
5.4.8.3-testnet Pre-release
Pre-release

Testnet release of 5.4.8.3 for testing. This is RC1 for 5.4.9.0 maintenance release as part of the Natasha milestone.

This is for testnet network only unless permission is granted to use on mainnet by a core dev.

5.4.8.2-testnet

10 Oct 14:52
b07ab3f
Compare
Choose a tag to compare
5.4.8.2-testnet Pre-release
Pre-release

Testnet release of 5.4.8.2 for testing.

This is for testnet network only unless permission is granted to use on mainnet by a core dev.

5.4.8.0-hotfix-1

03 Jul 14:17
2a53b46
Compare
Choose a tag to compare

This is a hotfix tag to address the breaking change in miniupnp API version 18+. Currently this is only necessary for Arch Linux with the latest updates.

Fixed

5.4.8.0-leisure

11 Apr 02:37
5.4.8.0
95b4c2e
Compare
Choose a tag to compare

[5.4.8.0], 2024-04-10, leisure

This release is a maintenance release that adds checkpoints post the unintended
fork when 5.4.6.0 was introduced. Given that some folks upgraded to 5.4.7.0 too
late for their wallets to correct out of the fork, some 5.4.7.0 clients continue
to spam the network. This will largely squelch that on 5.4.8.0 nodes. It also
will force the forked 5.4.7.0 or below clients to reset their blockchain and
resync from zero when they upgrade to 5.4.8.0 and run it for the first time.

It is highly encouraged to upgrade to this release.

Jim Owens

Added

Changed

  • build: enforce SSE2 on x86 targets #2746 (@div72)
  • consensus: Update checkpoint data for mainnet and testnet #2756 (@jamescowens)
  • gui, util: Enhance verify checkpoints fail handling; use RegistryBookmarks for DB passivation #2758 (@jamescowens)

Removed

Fixed

  • build, depends: fix compilation with XCode 15 #2747 (@div72)
  • Fix man page installation path for cmake builds #2749 (@theMarix)
  • consensus, mrc, sidestake: add mrc fees to staker to rewards to be allocated via sidestaking #2753 (@jamescowens)
  • Fix Systemd unit install location #2754 (@theMarix)
  • scraper: Corrections to scraper_net after removal of cntPartsRcvd decrement and increment #2755 (@jamescowens)
  • rpc: fix setban segfault #2757 (@div72)

5.4.7.0-leisure

13 Mar 04:15
5.4.7.0
2f4877b
Compare
Choose a tag to compare

[5.4.7.0], 2024-03-13, leisure

This release is solely to implement the disconnection of version 5.4.5.0 and
below nodes as the last cleanup action due to the inadvertent fork caused at
3190603/4 as a result of the inadvertent protocol change introduced in
5.4.6.0. A more detailed explanation is in order:

The default contract version is supposed to change from 2 to 3 at the block v13
hardfork, which was envisioned to be set as part of the Natasha milestone
release. The way this is accomplished is that the default contract version is
incremented to 3, and then logic is used to ensure the contract version actually
used is 2 until the v13 fork point is reached. The fork point for v13 was not
set in version 5.4.6.0, as it was intended to be 100% protocol compatible with
5.4.0.0 - 5.4.5.0, i.e. a leisure upgrade; however, a coding omission caused tx
messages sent from 5.4.6.0 nodes to be version 3 instead of version 2
immediately. This caused nodes 5.4.5.0 and below to reject the transaction
containing the message and the block causing a fork.

This mistake is mine and mine alone, and I am regretful about it. This is the
first forking incident we have had in a number of years, but I take this type
of event very seriously. Regression testing is done as well as longer time
testnet testing and some mainnet testing before that, but this particular type
of issue is hard to catch.

By the time this actually occurred on mainnet, there was far more weight on the
5.4.6.0 side of the fork than the 5.4.5.0 side, so it made the most sense to
continue forward with the 5.4.6.0 side, and require everybody that had not
already upgraded to upgrade, essentially turning 5.4.6.0 into a mandatory.

All but a few folks have upgraded now to 5.4.6.0, but we still have a few nodes
(with aggregrate difficulty ~ 1.0) on the 5.4.5.0 fork and these nodes are
connecting to 5.4.6.0 peers. Given that the fork common block is fairly deep at
this point (the fork point was at 3190603/4 and the head of the chain is at
3194579 as of this writing), this is causing a lot of unnecessary network
traffic between 5.4.5.0 and 5.4.6.0 nodes to pass orphan blocks around.

At this point it makes sense to implement an automatic disconnect for all nodes
5.4.5.0 and below. The code already disconnected nodes below 5.4.0.0 as the
protocol version in wallets less than 5.4.0.0 is out of date. Because the
protocol version was not incremented from 5.4.5.0 to 5.4.6.0, we have to
distinguish and disconnect here based on the node sub version string, which
contains 5.4.x (and is also displayed in the peers table).

Note this is similar in concept to what we do in a normal mandatory, where we
normally disconnect pre-mandatory version nodes after a grace period from the
hard fork height. Obviously the conditions are not ideal here, but this is the
best answer at this point.

This should solve the elevated CPU usage and network bandwidth of wallets that
are receiving all of the orphan block traffic.

This release also includes the small adjustment to the Fraction class to solve
the compilation problems on Arch.

Added

Changed

Removed

Fixed

5.4.6.0-hotfix-1

04 Mar 23:02
5.4.6.0-hotfix-1
325a127
Compare
Choose a tag to compare
This hotfix includes PR2748 which corrects test suite errors

This hotfix is only necessary if C++ compiler flag
-D_GLIBCXX_ASSERTIONS is set during build. Currently this is
true for Arch distribution.

This hotfix is NOT necessary for normal wallet operation.

5.4.6.0-leisure

02 Mar 22:24
5.4.6.0
3044941
Compare
Choose a tag to compare

[5.4.6.0], 2024-03-02, leisure, "Miss Piggy"

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.4.6.0

This is the 5.4.6.0 leisure release, the final release in the Miss Piggy
milestone.

This is an important release that contains a number of bugfixes that enhance
stability for the wallet and implement poll caching, automatic background
updates and performance improvements for polls/voting. It also includes most
of the basic machinery needed to support the v13 block version protocol which
will be in the next mandatory at the following milestone, Natasha, although the
v13 block height has not been set, so we remain at v12 for now.

Some highlights:

  • GUI control of sidestaking via settings -> options -> staking has been
    implemented. Sidestaking has been converted over to integer arithmetic to
    eliminate floating point consensus issues in preparation for the v13 mandatory,
    which will support mandatory sidestaking.
  • Caching of polls in the client with automatic background updating, and poll
    expiration reminders. This is a major improvement to polling. Some corrections
    were made to how the wallet handles "my vote" tracking.
  • CMake build system support, which allows CMake to be used instead of
    autotools. Note this does not yet work for Windows builds, but that is coming.
    This should be helpful for maintainers.
  • Removal of almost all OpenSSL dependencies in favor of upstream native
    implementations, with the exception of SSL RPC (deprecated anyway), and
    indirect use through CURL, which is required in the scraper and a few other
    areas.
  • A number of important fixes and updates, including a fix for the beacon
    history stall problem that some folks have experienced, and an issue that caused
    a major fork in testnet back in September 2023.
  • PR #2711 changes the JSON keys in the superblocks RPC command to lower snake
    case, which is the RPC standard. This could cause scripts that process the
    superblocks command output to fail, so a small adjustment to scripts that use
    that command may be necessary.

A number of people besides myself contributed to this release. I would like to
thank the following people:

It is highly recommended that EVERYONE upgrade to this release.

There is much planned for Gridcoin in the future. I encourage folks to join the
discussion on Discord to participate.

Jim Owens

Added

Changed

Removed

Fixed