Skip to content

Releases: gridcoin-community/Gridcoin-Research

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)

5.4.0.0-mandatory

31 Jul 21:08
5.4.0.0
c4ff381
Compare
Choose a tag to compare

[5.4.0.0] 2022-08-01, mandatory, "Kermit's Mom"

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

The Gridcoin core developers are proud to release 5.4.0.0 which represents the
Kermit's Mom milestone. This is a mandatory release and includes the long-
awaited implementation of Manual Reward Claims (MRC)
and significant
improvments to poll and project structures among many other enhancements and
fixes.

Highlights

Manual Reward Claims (MRC)

The importance of this release to the community cannot be overstated. One of the
most significant challenges to new "crunchers" joining the Gridcoin community
is the payment of the 2nd layer crunching rewards to the crunchers for work they
are doing for network approved BOINC projects. The implementation of constant
block rewards (CBR) a number of years back improved the participation of wallets
in the staking process dramatically, raising the average difficulty on the
network from about 3 to greater than 18 today, representing more than
180000000 GRC continuously online and staking. This has drastically improved
security of Gridcoin, making it much more resistant to 51% attacks, but has had
the downside of increasing the effective minimum GRC required to solo crunch
to 5000 GRC or more. Without MRC, which is in this release, solo crunchers are
required to stake to get paid their rewards.

Most people regard having enough GRC to stake on average once a month is the
practical minimum for solo crunching, so 5000 GRC is effectively the minimum
bar for entry for solo crunching. Needless to say this is a giant challenge
for many newcomers and greatly harms the growth of the network. The pools help
with the problem by providing a way to earn GRC and eventually collect enough
to solo crunch, but they have a drawback in that the project research when pool
crunching is done in the name of the pool, not the cruncher. MRC sweeps that
giant hurdle away. With MRC you can solo crunch with only about 1 GRC to start.
You simply need enough to send a beacon advertisement (which is the new solo
cruncher's way of letting the network know that they want to get rewarded for
crunching). MRC will now allow a solo cruncher with an active beacon to request
payment at intervals as small as 14 days from the last time they were paid.
There is no minimum payment threshold, only the minimum time threshold. This
request for payment is a "manual reward claim" request, which is where the name
MRC came from originally. Note that what is going on under the hood is that the
requester is sending out a "MRC" request contract that is attached to a
transaction in the Gridcoin blockchain, which is picked up by the next staker,
and causes the staker to stake the reward for the requester as a delegate.
Essentially MRC is a form of delegated staking. Note that for this privilege
the requester will pay a portion of their reward as a fee to the staker and the
foundation. The total fee starts at 40% of the rewards at 14 days and then
declines as 14/(number of days) as the interval between payments is increased.
The foundation gets 80% of the fees and the staker 20%. These ratios were set
and approved by official poll
(id 651a3d7cbb797ee06bd8c2b17c415223d77bb296434866ddf437a42b6d1e9d89,
gridcoin-community/Gridcoin-Tasks#250).

To give a specific example, a new cruncher registers their beacon and starts
crunching. They have a pretty good computer and their magnitude has been
building to the point where at 14 days they have about 35 GRC pending as
rewards. At 14 days after the activation of their beacon, the MRC payment
button on the main screen will allow them to request payment of their rewards.
If they press the button at 14 days, then the requester will get 35 * (1 -
0.40) or 21 GRC. The foundation will get 0.80 * 0.40 * 35 or 11.2 GRC and the
staker will get 0.20 * 0.40 * 35 = 2.8 GRC. If the cruncher waits until 28 days
to request the reward, lets assume his or her magnitude is constant, so the
rewards have doubled, so now the requester has 70 GRC pending. If they press
the button at 28 days, then the requester will get 70 * (1 - 0.20) or 56 GRC.
The foundation will get 0.80 * 0.20 * 70 or 11.2 GRC and the staker will get
0.20 * 0.20 * 70 or 2.8 GRC. Notice that the effective fee to the foundation
and the staker at 28 days is the same as at 14 days. This is by design. The
foundation and staker fees decline as a percentage from the point of view of
the requester's total rewards as the time between payment requests increase
beyond 14 days, but from the point of view of the foundation and staker, the
fees essentially are computed at the 14 day point and remain capped as absolute
numbers.

The MRC request button will appear on the wallet main screen for crunchers
with active beacons and will allow MRC requests once the block v12
functionality block height is reached. This is the post Kermit's Mom release
hardfork point, and it will be at block 2671700, which will occur on or about
August 31, 2022.

Some resources to review for MRC and related concepts:

Polls

Kermit's Mom has significantly improved both the rigor and functionality of the
polling system. Poll categories were included in the GUI rewrite a while back,
but those categories were GUI only and were not enforced by protocol at the
blockchain level. At the Kermit's Mom hardfork block (2671700), polls will now
use the poll payload v3 contract and associated protocol code, which will
enforce and validate poll categories and the validation rules associated with
them. Minimum poll duration and minimum vote weight percent of active vote
weight, along with poll type requirements are now encoded and/or enforced by
protocol. The GUI will display a "validated" tag for polls that have met
validation requirements for their given poll type. Polls that fail validation
requirements by the end of the poll will show "invalid". Polls with invalid
combinations of poll type, duration, and poll weight type cannot be created and
will also be validated by all nodes and rejected if an invalid combination is
received.

Polls also support the inclusion of additional fields, and the PROJECT poll
type now requires the additional fields of project_name and project_url in
the poll. This is in anticipation of driving automated whitelisting
functionality in a future release.

For more information, please see:

Projects

Kermit's Mom has implemented the inclusion of a GPPR controls required flag in
the project structure. After the Kermit's Mom hardfork point (2671700), all
project entries for the whitelist will require the GDPR protection flag to be
set to either true or false to indicate whether the project requires the user
to give permission for project statistics for that user to be exported. This is
used to drive a new column in the projects tab table in the researcher
(cruncher) wizard, and indicate a possible situation where a cruncher may not
have granted the necessary permission.

For more information, please see:

libsecp256k1 port from Bitcoin Core

This one is not visible on the outside to anyone, but is a major improvement to
Gridcoin's plumbing. @div72 did a fabulous job porting over Bitcoin Core's
libsecp256k1 to Gridcoin. This replaces OpenSSL for all elliptic curve
cryptography on the blockchain itself with Bitcoin's more efficient (and more
secure) version. OpenSSL is now only used by the CURL library for https
communication with external websites in the scraper project download. This will
remain as CURL is well encapsulated and well maintained.

There were many other improvements and fixes that are in the Kermit's Mom
release. Please refer to the change log below for details. This release was a
group effort. Thanks to everybody who submitted a PR merged into the release. A
special thanks to @barton2526 for doing many backports/fixes to the build
system, Qt version bumps, and other utility backports. Thanks to @Pythonix for
submitting backports and fixes to the network code. And thanks to @iFoggz for
submitting enhancements to the scanforunspent rpc. A special thanks to m3prx for
submitting the winning icon for MRC submission used in the GUI.

A teaser of the major feature to look forward to for the next milestone,
LaVerne: HD wallet support! This is another long sought piece of
functionality that will allow folks to store one keyphrase to regenerate all
keys if necessary and provide the foundation for proper hardware based wallet
functionality.

Jim Owens

[5.4.0.0] 2022-08-01, mandatory, "Kermit's Mom"

Added

Read more

5.3.3.0-leisure

27 Feb 17:30
5.3.3.0
ef1e69f
Compare
Choose a tag to compare

[5.3.3.0] 2022-02-27, leisure, "Janice"

The Gridcoin core developers are proud to release 5.3.3.0 which represents the
Janice milestone. This is actually a very large leisure release. On the surface
you will notice few changes, but there were a lot of updates under the hood,
including a number of bug fixes that should make the operation of the wallet a
lot smoother.

I would like to call out @barton2526 and @div72 specifically for their
contributions to this release. @barton2526 did a tremendous number of important
ports of functionality/changes/fixes from upstream. @div72 worked on some
critically important areas, including implementation of a Github integrated
automated release build capability, that will be used for this and succeeding
releases (See #2249.) There were other significant contributors too. Janice
was truly a group effort.

While this version is not a mandatory, I have noticed some nodes are still
running 5.3.0.0 or 5.3.1.0. In particular I STRONGLY urge folks running versions
prior to 5.3.2.0 to upgrade, as there have been many bug fixes since the
5.3.0.0 release that can affect the operation of the wallet, not to mention
the advancement of the GUI.

Enjoy. The next milestone is Kermit's Mom, which is going to be a mandatory and
will include some big items, including the long awaited MRC.

Jim Owens

Specific user notes:

  1. The -reindex option has now been implemented to allow rebuilding the block-
    chain transaction database from the block data file. This is similar to a
    bootstrap but uses the in-place blockchain data files instead. Similarly the
    existing -loadblock option has been improved to accept multiple data files.

  2. The blocks on the main screen will now show a percent progress indicator
    during sync.

  3. The CPID detection code in the wallet now prefers the CPID implied by the
    email configured in the wallet in the case multiple CPIDs are indicated in
    the boinc client_state.xml file (i.e. a potential split CPID situation).

  4. A privacy mode has been implemented for the GUI main screen that can be
    activated by Ctrl-Shift-M.

  5. -rpcwait and -rpcwaittimeout have been implemented following upstream
    behavior.

  6. Obsolete config settings are now removed from the config file to help
    eliminate confusion from no longer used settings and remove the old beacon
    keys (pre-Fern), which are no longer valid (and haven't been for a long time).

  7. Fix for the bug that would result in the current poll not being properly
    updated on the main screen, especially after a poll expires.

  8. Alt-7 was assigned as the hotkey for locking and unlocking the wallet in
    the GUI. (Alt-1 through Alt-6 select the Overview - voting buttons.)

[5.3.3.0] 2022-02-27, leisure, "Janice"

Added

Changed

Removed

Read more

5.3.2.0-leisure

01 Aug 23:46
5.3.2.0
fe6ab87
Compare
Choose a tag to compare

[5.3.2.0] 2021-08-01, leisure, "Ingrid"

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

This leisure release represents the completion of the "Ingrid" milestone. It
has turned out to be a very substantial release, quite a bit larger in scope
than originally envisioned. The biggest thing that folks will notice right away
is the re-skinning of the application to conform to the approved GUI assets that
were done for the GUI bounty. While a complete rewrite of a loosely coupled GUI
has not been completed, this is a great stop-gap until that is done.

Some highlights:

  1. Implementation of the GUI assets in
    #847 as native Qt.
    This major re-skinning is meant to tide us over until the implementation of the
    GUI as bountied in
    #1401.

  2. Many fixes and refinements to the GUI's underlying style and scaling. The
    wallet has a consistent look and feel across all platforms and most screen
    resolutions. There may be some remaining fine-tuning to dialog box sizes and we
    will attend to that in the next release after feedback from users in production.

  3. Overhauling of the poll/voting GUI. More work needs to be done in this area
    still, but the improvements in here should make voting a much better experience.

  4. Port of Bitcoin's ArgsManager which allows for much better processing of
    program arguments on the command line and the config files, and provides the
    plumbing for read-write core wallet settings into a new gridcoinsettings.json
    file while the wallet is running. Note that settings stored in
    gridcoinsettings.json always override the read-only gridcoinresearch.conf. (See
    7.)

  5. Implementation of the consolidate unspent wizard for graphically assisted
    selection of UTXOs to consolidate and automated construction of the
    consolidation transaction. (Prior to this to do UTXO consolidation required the
    use of the consolidateunspent RPC command in the debug console.)

  6. Refresh of rainbymagnitude to require a minimum of 1000 GRC to do a network
    rain, and also prevent dust distribution via rain. No payment to an individual
    as part of a rain of less than 0.01 GRC is allowed. The ability to send custom
    rain messages has also been removed. The ability to do a trial run of the rain
    transaction before the send to understand what is going to happen has been
    implemented.

  7. The implementation of new options that allow in wallet GUI control of staking
    and stakesplitting without having to shut the wallet down first. In wallet GUI
    control and configuration of sidestaking is envisioned for the next release.

  8. Refresh of the snapshot download functionality to ensure broader
    compatibility and more reliable operation across all platforms, and
    implementation of the "reset blockchain data" option to easily wipe the
    blockchain from the GUI or the command line and start syncing from zero without
    having to manually go and delete the files.

  9. Refresh of the diagnostics to provide better information and eliminate bugs
    within the diagnostics themselves in corner cases.

  10. Many other fixes and refinements.

Some known remaining issues (both predating this release):

  1. Snapshot download functionality still will not work correctly on some 32-bit
    Linux platforms due to the distributions not properly compiling the libzip
    package with 64 bit file offsets enabled. We are probably going to end up
    distributing a version of libzip in the main source code compile tree, just like
    LevelDB, ensure it is statically linked into the executable, and ensure it is
    properly compiled with large offset support to fix this issue across all
    platforms. Note that the platforms that seem to be most affected by this are ARM
    32-bit SBCs. The reason this is an issue at all is that the snapshot file is now
    greater than 2 GB. Windows 32 bit platforms work correctly and are not affected
    by this issue.

  2. If coin control is used to manually select UTXOs for a send, and a message is
    provided, the fees calculated do not include the cost of the message (0.1 GRC),
    so if the amount post fees to send + the calculated fees equals the selected
    UTXO size, the transaction will fail. This normally will not be a problem if
    automatic input selection is used, or you can simply reduce the amount to send
    by another 0.1 GRC and it will succeed.

Detailed notes on the new gridcoinsettings.json file and the listsettings and changesettings RPC commands:

With the implementation of the Bitcoin ArgsManager in Gridcoin comes the new
gridcoinsettings.json file. This file contains settings changed by the node
while running and settings stored in this file override the read-only settings
in the gridcoinresearch.conf file.

Two new RPC commands have been implemented to enable listing and change of
settings while the wallet is running:

listsettings takes no arguments and provides a JSON output of all settings
currently active in the wallet. For each setting it shows whether that setting
is changeable dynamically while the wallet is running without requiring a
restart.

If a setting does not require a restart of the wallet (i.e.
changeable_without_restart is true), then the setting(s) can be dynamically
modified by...

changesettings setting1=value1 setting2=value2 etc.

No dashes are required for the settings (think about them like entries in the
config file).

Note that settings modified this way will make entries in the
gridcoinsettings.json file and they will override any corresponding settings
in the gridcoinresearch.conf file.

The GUI control of staking and stakesplitting makes use of the same services
internally.

Enjoy!

[5.3.2.0] 2021-08-01, leisure, "Ingrid"

Added

Changed

Read more

5.3.1.0-leisure

04 Apr 18:52
5.3.1.0
7a5a96f
Compare
Choose a tag to compare

[5.3.1.0] 2021-04-04, leisure

This leisure release is part of the "Ingrid" milestone and contains a number
of important fixes. It is highly recommended to upgrade as soon as practicable.

Some highlights:

  1. The beacon renewal chain walker fix (#2054) corrects a potential stall on restart
    if the accrual directory is rebuilt.

  2. Beacons are not supposed to be auto-renewed during the scraper active period to
    prevent problems with magnitude for renewed beacons on the following superblock. We
    actually saw this, where a researcher lost magnitude on the following superblock (only)
    due to a renewal that occurred while the scrapers were active, and traced it to an
    incorrect guard on the renewal. #2090 and #2092 fix this problem.

  3. Checkpoint based spam protection has been reimplemented (#2084) and we are now
    verifying hardened checkpoints on startup to catch some forked wallets better.

  4. Several GUI improvements, including better researcher status while out-of-sync to
    prevent confusion (#2068), and an update to translations.

  5. Memory optimization for the beacon db to "passivate" unneeded beacon elements from
    memory.

  6. Implementation of a new getburnreport RPC function.

The next release should have the requested "sync-from-zero" menu option to complement
the "snapshot download" option already present.

Enjoy!

[5.3.1.0] 2021-04-04, leisure

Added

Changed

Removed

Fixed

5.3.0.0-mandatory

16 Mar 21:37
5.3.0.0
7f75aec
Compare
Choose a tag to compare

[5.3.0.0] 2021-03-16, mandatory

EMERGENCY MANDATORY

First, I would like to apologize for having to issue an emergency mandatory release. The newbie bug was ALMOST squashed by the
combination of 5.2.0.0+ and the hard fork and following superblock. Unfortunately almost is not good enough. There were 130 people
affected by the newbie bug, and after the post hard fork superblock, the pending rewards matched properly for 127 out of the 130
original mismatches. The other three didn't, and further, different nodes showed different things for those three. Most nodes showed
a perfect match but some showed a mismatch on one or two of the three involved. Many thanks to @div72 for a keen eye in helping me
spot the one line in code that was causing the problem.

Given different nodes don't match, this is a consensus issue and requires a mandatory to fix. Note that this version, when installed
and first run will automatically rebuild the accrual snapshots (in the accrual folder) to straighten everything out. This may
take a couple of additional seconds on startup, but should be transparent.

There are no other changes in this mandatory. Not installing this mandatory risks your node forking if it has a different accrual
than the rest of the network for those three newbie CPID's if they stake, so it is best to upgrade to this version ASAP.

We have run audits on a number of nodes with a hotfix version of this mandatory that we tested on mainnet last night and all now
match. This should be the end of the newbie bug problem and things should be quieter on the release front for a while!

Onward!

Thanks!

[5.3.0.0] 2021-03-16, mandatory

Fixed

5.2.2.0-leisure

14 Mar 22:24
5.2.2.0
50b3067
Compare
Choose a tag to compare

[5.2.2.0] 2021-03-14, leisure

This is a small maintenance release to address a sync from zero issue in the 5.2.1.0 release.

We had a report of folks sticking at block 2069264 during a sync from zero using 5.2.1.0. This did not occur with 5.2.0.0.

Looking into the matter, the bug fix in 5.2.1.0 (#2036) created a different problem where in a rare instance multiple beacon contracts
on the same block would not get recorded properly. The fix is in this release.

Folks that are using 5.2.1.0 should upgrade at their earliest convenience, because there is a small chance this problem could occur on a
future block. Note that if you were using 5.2.1.0, when you first start 5.2.2.0, it may take a little longer to startup at the Gridcoin
screen, because it has to scan to correct the problem caused 5.2.1.0.

Thanks!

[5.2.2.0] 2021-03-14, leisure

Fixed

  • beacon, contracts: Fix sync from zero issue due to ApplyContracts problem in 5.2.1.0 #2047 (@jamescowens)

5.2.1.0-leisure

08 Mar 01:12
5.2.1.0
90d00b6
Compare
Choose a tag to compare

[5.2.1.0] 2021-03-07, leisure

This is a small maintenance release to address some rough edges in the 5.2.0.0 release.

  1. The locked file during cleanup error that people were encountering when using the snapshot download menu option
    has been resolved.

  2. The workflow on the voting tab has been changed to mitigate the wallet being stuck for a long period of time
    every time the voting tab is selected. Now the polls do not load until the reload button is pressed. A timer
    keeps the data in cache for 60 minutes, and then puts up a reminder to refresh because it is stale. Switching
    away and switching back the data is retained.

  3. A very minor issue was corrected in the beacon db that under certain very improbable circumstances could cause
    a wallet to stall if restarted on a block where a beacon renewal contract is advertised, and on restart a reorg happens
    that causes the wallet to reorganize deeper than that block. The wallet will recover by being restarted again and the
    actual renewals are not affected by the problem, but it is a good idea to apply this release for the fix.

  4. Consolidateunspent was enhanced slightly by adding the transaction hash and fees paid to the rpc output.

Enjoy! :)

[5.2.1.0] 2021-03-07, leisure

Added

Changed

  • gui, voting: Make some minor adjustments for VotingDialog flow #2041 (@jamescowens)

Fixed

  • beacon, util, gui: Fix small error in beacon db for renewals and fix snapshot download functionality #2036 (@jamescowens)

5.2.0.0-mandatory

01 Mar 02:57
5.2.0.0
454f103
Compare
Choose a tag to compare

[5.2.0.0] 2021-03-01, mandatory, "Hilda"

The core team is proud to present the Hilda milestone release, which is a mandatory upgrade.

The mandatory aspect of the upgrade here is the complete fix for the "newbie bug" that was
not completely fixed in Gladys. This mandatory provides a permanent fix for the bug, and
also will pay newbie's back accrual when they stake post-fix to the point of their original
beacon confirmation superblock, as long as they have not already staked with their CPID. (For
reference, the "newbie bug" is where newly confirmed beacons would have their accruals
reset to zero at each superblock instead of continuing like they are supposed to.)

The transition height ("hard fork") is at 2197000, which will be approximately Sunday, March 14.
All nodes MUST be upgraded by then or face disconnection from the network. There is a disconnection
grace period of 2000 blocks higher than the hard fork, or 2199000. Any node not on 5.2.0.0 at that
time will automatically be disconnected.

In addition to the mandatory inducing changes, this release contains LOTS of goodies that should
improve the experience with the wallet. Some highlights:

  1. A Port of the data directory dialog box from Bitcoin Core for a brand new installation, allowing
    a different directory than the default to be specified. This will be memorized by the wallet as
    an alternative to providing a -datadir value on the command line. This should be especially useful
    for MacOS folks.

  2. Another goodie for the MacOS folks is the implementation of the AppNap manager ported from Bitcoin Core,
    which suspends AppNap when the wallet is staking to avoid lost stake opportunities.

  3. Significant optimizations were done to memory usage that reduce memory requirements by 30% or more.
    This should really help using the wallet on SBCs and also reduce hardware requirements on other
    platforms. It also results in another modest improvement in sync speed, although we are getting
    to the point of diminishing returns there. Mainnet can sync from zero in less than 2 hours on a
    fast machine.

  4. Several bottlenecks were removed in the GUI code that caused the wallet to bog down very badly
    if the wallet has a lot of transactions or a lot of UTXOs. This drastically improves the GUI experience,
    especially if resyncing an existing wallet from zero with the blockchain, or on a slower SBC.

  5. The GUI now remembers the size and position of the wallet window for both mainnet and testnet, and some
    font work was done to improve scaling on various displays. (The font and scaling work is still a
    work in progress, but it is much better than before.)

  6. A big bug was fixed in CreateTransaction that was causing insufficent fee transaction rejections
    and driving everyone crazy! This bug has actually been in there forever and is finally slayed!

  7. Related to #3, but also generally useful for folks interested in monitoring their staking
    efficiency are new measures in the getmininginfo RPC: staking_loop_efficiency measures the percent
    of elapsed time that is covered by an active staking loop, and staking_efficiency measures the overall
    staking efficiency, which takes into account staking_loop_efficiency and the UTXO's that are on
    cooldown.

  8. The beacon registry in the wallet, which holds in memory the beacons for the network, has received
    enhancements that solve some thorny problems related to contract lookback and beacon renewals, and
    does this with high performance by using leveldb for specialized storage of the beacon structures.

  9. Consolidateunspent has been enhanced. The function now allows the consolidation of ALL addresses
    to the specified address, and also allows the sweeping of associated change addresses.

  10. The wallet no longer depends on external IP resolvers, but instead uses the Bitcoin Core style of
    IP resolution. This also means the wallet will correctly update its IP if a notebook is put to sleep
    on one network and then awoken on another with a different IP. Before the wallet would have to be restarted
    to accept incoming connections. Note that UPNP can still be an issue though.

  11. Other bugfixes and enhancements too.

This was a pretty hefty release. We hope you enjoy it! :)

[5.2.0.0] 2021-03-01, mandatory, "Hilda"

Added

Changed

Removed

Fixed