Skip to content

Releases: gridcoin-community/Gridcoin-Research

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

5.4.5.0-leisure

23 Apr 06:46
5.4.5.0
1c6227b
Compare
Choose a tag to compare

[5.4.5.0] 2023-04-23, leisure

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

This is an important leisure release and follows right on the heals of
5.4.4.0, because we fixed one thing only to break another in a worse way. By
worse I mean that some people with old keys could get a corrupt wallet message
on startup. In troubleshooting this issue, as it turns out, there is more to
the story than just the compressed flag not being set properly. Gridcoin has
been around a long time. A number of older wallets may have keys generated by
openssl that aren't handled correctly by the secp256k1 DER parser. We switched
over to secp256k1 from openssl for keys in 5.4.0.0, to align with Bitcoin
upstream. It is not entirely clear why Bitcoin does not see this issue with old
keys. Regardless, to be safe, we have disabled the ability to import HEX
formatted keps with importprivkey. This loss of HEX import functionality should
affect essentially no one, since the Base58, WIF, form is what everybody uses.

It is highly recommended that EVERYONE upgrade to this release.

Added

none

Changed

none

Removed

none

Fixed

5.4.4.0-leisure

21 Apr 20:44
5.4.4.0
d655ee5
Compare
Choose a tag to compare

[5.4.4.0] 2023-04-21, leisure

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

This is an important leisure release. It is not mandatory but contains an
important bug fix for exporting and importing private keys which has been
present since the last mandatory, 5.4.0.0. For releases between 5.4.0.0 and
5.4.3.0 inclusive, dumpwallet and importwallet work correctly, but dumpprivkey
and importprivkey do not.

It is highly recommended that EVERYONE upgrade to this release, especially if
you are using dump and import rpc functions for keys.

Added

none

Changed

none

Removed

none

Fixed

  • wallet, rpc: Add missing assignment of fCompressed in dumpprivkey #2680 (@jamescowens)

5.4.3.0-leisure

05 Apr 21:27
5.4.3.0
57b2ff9
Compare
Choose a tag to compare

[5.4.3.0] 2023-04-05, leisure

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

This is a very small intramilestone leisure release to integrate a few hotfixes
after 5.3.2.0.

In particular the workaround for backup wallet is important for those running
Linux with Boost 1.74 and whom have replaced the usual walletbackups
subdirectory with a symlink to another volume to redirect the automatic backups.

Added

  • install: Enhance windows installer - detect running gridcoinresearch(d).exe and ask to close before continuing #2672 (@jamescowens)
  • gui: Add one minute QTimer to update beacon age/expiration in tooltip #2671 (@jamescowens)

Changed

none

Removed

none

Fixed

  • util: Implement workaround for backupwallet to deal with Boost 1.74 regression on copy_file #2669 (@jamescowens)
  • banman: use GetPerformanceCounter instead of GetRandBytes #2668 (@div72)

5.4.2.0-leisure

26 Mar 03:06
5.4.2.0
4741869
Compare
Choose a tag to compare

[5.4.2.0] 2023-03-26, leisure, "LaVerne"

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

This is the 5.4.2.0 leisure release, the final release in the LaVerne milestone.

The changelog for this release is shorter than usual, but don't let that fool
you! Here are the most significant features in this release:

  1. #2540: HD wallet functionality (BIP32, but NOT BIP39 seed phrase support).
    See details below.
  2. #2620: Inclusion of Berkeley DB version 5.3 in tree and standardization of
    all wallet.dat files to the bdb 5.3 format. THIS IS VERY IMPORTANT See
    details below.
  3. #2619: Optimization of critical section locking during poll refresh to fix
    non-responsive GUI with wallets that have slow disks. This addresses the
    complaint of non-responsive GUI when there are a lot of polls in progress and
    the poll refresh is done on a computer with a regular HDD.
  4. #2645, #2659: Improvements to the MRC request screen to improve information
    and reduce confusion.
  5. #2624: Update of pool cpids and avw rules. This adds the new pool (GRC Pool
    5) to the list of valid pools for pool mode and also updates the poll % AVW
    requirements passed by governance poll "Adopt New AVW Percentage Requirements
    for Polls" c186e2fd5fa81541e74838c1f3b1268c471b55dc6c37aa1b3b9ea84ecd20801c.
  6. #2612: Backport of Bitcoin Core ARMv8 SHA2 intrinsics which should speed up
    newer ARM devices that are running a wallet.

For HD wallet functionality, please see the documentation in the PR:
#2540. Note that
people with existing wallets that choose to upgrade will have a HYBRID wallet
that contains both legacy private keys, the new hdseed key, and keys that are
generated from the hdseed. Backing up the hdseed covers all of the keys
generated from the hdseed, but not legacy keys. Those must also be backed up. It
is still safest to store copies of the wallet backup file(s) automatically
stored by the wallet every 24 hours in the walletbackups subdirectory of the
wallet data directory.

We have not yet implemented seed phrase support (BIP39).

IMPORTANT
If you are running a Windows wallet or certain Linux distribution wallets that
use the older Berkeley DB 4.8, such as Fedora or OpenSUSE, your Berkeley DB
version of your wallet.dat file will be upgraded automatically to 5.3 when you
first run Gridcoin after upgrading to this release. This should be completely
transparent to you. If for some reason you decide to downgrade, you need to be
aware that the older release will NOT successfully read your wallet.dat file
without doing a special procedure. If you downgrade to 5.4.1.0 or earlier,
before starting the downgraded wallet, you need to go to the data directory,
which is at %AppData%\GridcoinResearch on Windows or ~/.GridcoinResearch on
Linux by default, and go to the database subdirectory and delete the log.* files
found there. Then you can start the downgraded client and it should be able to
successfully read your wallet.dat file. If you downgrade and forget to do this,
your wallet will warn you about an unrecoverable error. If so, shut the wallet
down, and perform step discussed above, then restart. THIS IS ONLY NECESSARY IF
DOWNGRADING FROM THIS RELEASE.

The advantage of having everyone on the same bdb version, 5.3, is that
wallet.dat files will now be portable across ALL of Gridcoin's supported
operating systems/architectures that are on this version or higher (or were
already running bdb 5.3, such as Debian/Ubuntu, Mint, and Arch for example).
Just remember if you take a wallet.dat that is running on this release and move
it over to a machine running an earlier release on Windows, you will need to do
the procedure above or you will run into an error trying to read the
wallet.dat. Alternatively you can upgrade the target machine's wallet
installation before moving the wallet.dat, which would be preferred.

Thanks to the following contributors for this release:

  • barton26
  • delta1513
  • div72
  • jamescowens
  • PrestackI
  • pythonix
  • sitiom
  • theMarix

Enjoy!

Jim

[5.4.2.0] 2023-03-26, leisure, "LaVerne"

Added

Changed

Removed

none

Fixed

  • net: Turn net structures into dumb storage classes (backport) #2561 (@Pythonix)
  • build: Include native_X.mk before X.mk #2609 (@barton2526)
  • depends: fix OpenSSL for Darwin builds #2610 (@div72)
  • build: Change actions runner image to Focal, Force Lint to use 22.04, Change cd runner version #2611 (@barton2526)
  • gui: don't show datadir error msgbox if arg isn't specified #2617 (@div72)
  • rpc: Repair auditsnapshotaccrual rpc function #2621 (@jamescowens)
  • gui: Correct updateBeaconIcon() function in bitcoingui.cpp #2622 (@jamescowens)
  • wallet: Strengthen CWalletTx::RevalidateTransactions #2627 (@jamescowens)
  • test: Fix Wambiguous-reversed-operator compiler warning, drop boost::assign #2632 (@barton2526)
  • gui: Fix wallet overview displaying lower-case poll name #2640 (@delta1513)
  • Fix and optimize ResendWalletTransactions #2642 (@jamescowens)
  • build(nsis): Write registry keys to HKLM instead of HKCU, Install shortcuts for all users, Fix INSTALLDIR removal bug #2643 (@sitiom)
  • gui: Fix TransactionRecord::decomposeTransaction to properly display self-sidestake #2647 (@jamescowens)
  • rpc: Fixed the RPC error when running help voting while syncing #2649 (@delta1513)
  • build: Fix compilation with GCC 13 #2653 (@theMarix)
  • rpc: Formatting - typo correction rpc help for listresearcheraccounts #2654 (@PrestackI)

5.4.1.0-leisure

27 Nov 20:20
5.4.1.0
6a4285a
Compare
Choose a tag to compare

[5.4.1.0] 2022-11-27, leisure

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

This is the 5.4.1.0 leisure release, an intramilestone maintenance release as
part of the LaVerne milestone. Much of this release comprises bugfixes and
updates from the Bitcoin Core upstream. Thanks to @barton2526 for working hard
to port Bitcoin Core PR's for Gridcoin. There are a few notable features that
make this version an important upgrade:

  • Implementation of the getmrcinfo rpc function, which reports summary and/or
    detailed MRC info for a single CPID or the entire network.
  • Implementation of the new core diagnostics library, along with an associated
    walletdiagnose rpc command to allow running diagnostics on a headless wallet.
    The GUI diagnostics were refactored to use the new core library. Thanks
    @MinaFarhan!
  • Implementation of wallet holder's last vote information on the GUI poll
    cards. This allows you to see your last vote on each poll in the GUI.

Thanks to the following contributors for this release:

Enjoy!

Jim

[5.4.1.0] 2022-11-27, leisure

Added

  • net: Add and document network messages in protocol.h (backport) #2533 (@Pythonix)
  • Define MAX_DIGITS_BTC for magic number in BitcoinUnits::format #2555 (@barton2526)
  • rpc: Implementation of getmrcinfo #2570 (@jamescowens)
  • init: Add init error message if -printtoconsole and -daemon specified simultaneously #2571 (@jamescowens)
  • rpc: getmrcinfo part 2 - add calculated minimum fees and fee boosting and by CPID reporting #2575 (@jamescowens)
  • fs: fully initialize _OVERLAPPED for win32 #2587 (@div72)
  • util: Diagnose Lib Version #1 #2573 (@MinaFarhan)
  • util: Implement core diagnostics #2 (@jamescowens)
  • util: modify Win32LockedPageAllocator to query windows for limit. #2536 (@div72)
  • gui, voting: Implement information for wallet holder's votes on poll info cards #2605 (@jamescowens)

Changed

Removed

  • refactor: remove unused c-string variant of atoi64() #2562 (@barton2526)
  • refactor: Remove unused CDataStream::rdbuf method #2585 (@div72)

Fixed

  • net: Fix some benign races (backport) #2532 (@Pythonix)
  • rpc: fix invalid parameter error codes for {sign,verify}message RPCs #2556 (@barton2526)
  • build: Fix x86_64 <-> arm64 cross-compiling for macOS #2560 (@barton2526)
  • rpc, mrc: Fix field name and initialization of mrc_fees_to_staker #2567 (@jamescowens)
  • gui: Add missing resizeTableColumns to fix send address book column widths #2569 (@jamescowens)
  • accrual: rebuild snapshot registry on corruption instead of crashing #2577 (@div72)
  • doc: Fix link to MurmurHash3.cpp (moved from Google Code to Github) #2584 (@div72)
  • fix help text for revokebeacon command #2591 (@Pythonix)
  • util: Fix spelling error in gridcoinresearchd.cpp #2590 (@jamescowens)
  • depends: always use correct ar for win qt build #2588 (@div72)
  • util: Fix some bugs due to new implementation and change in BOINC dir handling (@jamescowens)
  • util: Diagnose lib - Implement changes to solve crash on some Boost 1.66 machines #2597 (@jamescowens)
  • contrib: Check for patch command, Check for wget command #2594 (@barton2526)
  • build: Check std::system for -[alert|block|wallet]notify #2582 (@barton2526)
  • gui: Changed the wording on the tooltip for the address book #2602 (@delta1513)
  • build: pass win32-dll to LT_INIT() #2601 (@barton2526)
  • build: minor cleanups to native_clang package #2600 (@barton2526)
  • util: restore translations to diagnostics #2603 (@jamescowens)
  • refactor: Fix problems found by valgrind #2607 (@jamescowens)