Skip to content

v4.7.0

Latest
Latest
Compare
Choose a tag to compare
@crowetic crowetic released this 22 Jan 05:33
v4.7.0
faee7c8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Qortal Core V4.7.0

Changes in this release:

This release marks a significant step forward in the project history. The removal of the ability to self-sponsor, and the removal of any type of additional rewards given to 'founders' from consensus.

  • All changes proposed in the 'crowetics-proposals' website have been included in final versions in this release.

  • The only changes that have NOT been made that were so proposed, are the removal of blocksMintedAdjustment from credit towards blocksMinted. This change will take place in a subsequent release.

  • featureTriggers created:

"adminsReplaceFoundersHeight": 2012800,
"nullGroupMembershipHeight": 2012800,
"ignoreLevelForRewardShareHeight": 2012800,
"adminQueryFixHeight": 2012800

  • All featureTriggers will take place on the same block.

  • Rewards Modifications, and GROUP_APPROVAL changes (making the MINTER group - ID 694) able to be controlled by way of GROUP_APPROVAL.

  • After featureTrigger activates, MINTER group will be transferred to 'null account', and will subsequently from then on be controlled by way of GROUP_APPROVAL from the admins of the MINTER group (A.K.A 'Minter Admins').

  • Q-App with the name Q-Mintership will be a tool utilized by both new and existing minters, and Minter Admins, by which to be added or removed from both the MINTER group itself, and admins therein. Utilizing this app, a user wishing to have rights to mint on the Qortal Network, will present themselves by way of a 'card' submitted to the 'MinterBoard' containing any information they choose to publish. This information may include links to QDN published websites/applications/data/Q-Blog posts/Q-Tube videos/etc. Armed with this information, the Minter Admins, a community-elected group of individuals from all over the world, will be able to approve or deny minting rights assigned to an account by way of 40% (or more) of said Admins submitting GROUP_APPROVAL transactions.

  • This update marks a SIGNIFICANT re-build and essentially a 're-birth' of the Qortal 'minting' consensus mechanism, and was implemented to combat the 'one game' that could be played against the previous version, nicknamed 'self-sponsorship'. It was always known that this game would become a concern and would have to be dealt with, and this release is the initial action dealing with it.

  • Along with the 'Mintership' proposal modifications, a significant modification of the Qortal Consensus REWARDS SYSTEM has also taken place. Since the Genesis of the project, minting was meant to reward 'contribution over time'. Now, it more efficiently does so with the rewards distributions now no longer being heavily weighted in favor of the 'founder accounts'.

  • Founder accounts on Qortal are now nothing more than a label, giving credence to accounts owned by those that submitted effort pre-Genesis that without such effort would have prevented the project from having a Genesis.

  • From block 2012800 and beyond, rewards will be distributed as follows:

The previous percentages that were given to 'founder' accounts (flags: 1) will be given to the Minter Admins and Developer Admins at an even 50/50 split. Along with those, the 'additional' that would be going to minters in the level 9-10 rewards tier, will also be split in the same fahion.

Minter Admins must be minting in order to obtain rewards. Developer Admins do not have a minting requirement. This was done because the developer admins do not utilize their developer accounts to mint, and never have. They maintain separate minting accounts. Therefore a minting requirement being added to the Developer Admins would not have made sense. Instead, the Developer Admins will be actively contributing toward the project by way of development, and if they are not, they will be removed from the Developer Admins.

In the future, a method to keep track of 'activity' for both Minter and Developer Admins (outlined in the original proposal documentation) will be added as well. This will measure initially, the GROUP_APPROVAL signatures from both groups of Admins. Utilizing this information, an 'activity' determination will be made, and only active Admins will be given the vast majority of the rewards. However, until this modification is made, no activity requirement is currently added in 4.7.0.

  • Founder accounts will no longer be treated any differently than any other minting account, and will be given only the rewards entitled to their minting level tier based on their minting activity verified by minting signature submissions. Just like any other minter.

  • Additional fixes for the MINTER validation have also been made.

  • 'Reward Share' transactions will no longer require level 1 to be created, instead, only being part of the MINTER group controls the creation of reward_share tx (utilized for 'minting keys')

qortal.jar

MD5: 1958d4c191d242aa65829adde1c1ab3d qortal.jar
SHA1: 6caec685aa328315f93f8c6c0033e5f97b346aef qortal.jar
SHA256: fd1ff954910f69446e720885054d9af91c473dbcb01e1894d082edcf0a0537bc qortal.jar

qortal.exe

MD5: c79583894287590ae30a109b4131e761 qortal.exe
SHA1: a539cd286e27a9ef470455fb08a7ddf0677626f2 qortal.exe
SHA256: 181cd7e861a67f39f000a4e6c7acd62d2ada3a88bfd47e648a78cdf514685dc1 qortal.exe

VirusTotal report for qortal.exe

qortal.zip

Contains bare minimum of:

  • built qortal.jar
  • log4j2.properties from git repo
  • start.sh from git repo
  • stop.sh from git repo
  • qort script for linux/mac easy API utilization
  • printf "{\n}\n" > settings.json

All timestamps set to same date-time as commit, obtained via GitHub API.
Packed with 7z a -r -tzip qortal.zip qortal/

MD5: 08b02cfdd467fd16bec46b38e7c51783 qortal.zip
SHA1: a2932f75486e130963c50ec1ff34ac870910b12a qortal.zip
SHA256: 0ae8bec807b635e7f7a541e13b18cd9158fb564213adc20744a6443711833d04 qortal.zip

What's Changed

  • Balance Recorder & Hard Forks by @kennycud in #244
  • bump version to 4.7.0 and set featureTrigger block heights by @crowetic in #245
  • updates/fixes to publish-auto-update.pl by @crowetic in #246
  • push featureTrigger blocks back a bit to give more time to prepare+sign auto-update by @crowetic in #247

Full Changelog: v4.6.6...v4.7.0

Contributors

crowetic and kennycud
Assets 5
Loading