Qortal Project

The future of blockchain platforms

User Tools

Site Tools

Trace:
qortal_status_updates

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
qortal_status_updates [01/17/2024 17:55] – magic_inkqortal_status_updates [03/03/2024 13:13] (current) – cal
Line 1: Line 1:
-====== Qortal Status Updates ======+====== Qortal Status Updates (old page) ======
  
 {{:qortal_official_logo_transparent_.png?400|}} {{:qortal_official_logo_transparent_.png?400|}}
  
-This page will contain information about the current status of the Qortal Project, any known upcoming additions, and whatever else to be aware of. The person’s messages being relayed referring to “I” is @crowetic FYI. Times are based on Pacific Standard Time (PST).+This page will not be updated - please refer to https://wiki.qortal.org/doku.php?id=status_updates for current updates after Feb 20th 2024
  
-**CURRENT CORE VERSION:** 4.4.2+**CURRENT CORE VERSION:** 4.5.1 (Feb 18th 2024)
  
-**CURRENT UI VERSION:** 4.4.4+**CURRENT UI VERSION:** 4.5.0
  
 **CURRENT BLOCK REWARD:** 3.50 QORT* **CURRENT BLOCK REWARD:** 3.50 QORT*
Line 19: Line 19:
 **CURRENT TRADE FEE:** 0.011 QORT **CURRENT TRADE FEE:** 0.011 QORT
  
 +
 +
 +===== February 18th 2024 =====
 +
 +@here **Qortal Core version 4.5.1 auto-update has been signed**
 +
 +Network will begin updating shortly.
 +
 +
 +
 +===== January 30th 2024 =====
 +
 +
 +
 +**CORE version 4.5.0 has been pushed with Algo resolution. **
 + <code> "penaltyFixHeight": 1589200 </code>
 +
 +The block above will activate the fix. As of the update itself network state will be corrected. As of the block, all minters penalized in previous incorrect SelfSponsorshipAlgoV1 run, will be restored to previous state.
 +
 +
 +**@here Qortal UI version 4.5.0 has been released**
 +
 +**UI version 4.5.0 Changes include:**
 +
 +- Disabled tour with api popup
 +
 +- Fixed metadata issue on q-apps page
 +
 +- Fixed bootstrap button auto-check and pop-up message
 +
 +- Added file check and backup url for built-in java downloads
 +
 +- Added Finnish translations
 +
 +- Updated dependencies
 +
 +- Minor Fixes
 +
 +https://github.com/Qortal/qortal-ui/releases/tag/v4.5.0 
 +
 +for Mac, use this for now:
 +https://github.com/QuickMythril/qortal-ui/releases/tag/v4.5.0
 +
 +===== January 29 2024 =====
 +
 +@here **Status Update** - Core Development - **Algo issue resolution.**
 +
 +We are not quite done with the algo fix release. But we are close. This is by far the most important thing going on right now overall, and we are putting a LOT of time into it.
 +
 +At this point, it seems like **Stage 1 will be ready for release TOMORROW** - most likely about this time tomorrow. 
 +
 +Please be patient as we ensure that the fix is 100% good in every way, and get it rolled out. We CANNOT rush this, as there is ZERO room for error. It MUST be done 100% correctly. 
 +
 +Below are the **two stages required for the next 2 updates.**
 +
 +**Stage 1** - take the network state back to the way it was prior to the too-sensitive-algo run. - This means all changes that the incorrect algo run made. Every account with a penalty assigned by the previous run, will go back to the way they were prior. **Blocks Minted Penalty will be set back to whatever it was prior to the previous run.** Chain state will go back to the way it was prior, and we will be ready to implement V2.
 +
 +**Stage 2** - Implement **SelfSponsorshipAlgoV2**.  Modifying SSAlgoV1 was not the correct way to implement this, and as such, will be implemented differently. **SSAlgoV2 becomes a thing and activates.**
 +
 +These two updates **will require two separate releases, and two very complex and important modifications** that cannot be rushed. We must ensure that everything is done correctly in every way, as to ensure we can get the network to where it should be only, and ensuring there is no potential for network state confusion.
 +
 +Thank you for your patience and understanding. Will make further announcements as necessary.
 +===== January 21 2024 =====
 +
 +@here - After an entire day of reviewing data understanding the reasons for the 'over-sensitive' algo run yesterday, we have come up with the methods that will be utilized to ultimately solve the problem. Please see the information below, and file attached for more details.
 +
 +- It was discovered that the algo can essentially be set to '**positive mode'**, instead of adding a NEGATIVE to blocksMintedPenalty, the algo can be programmed to re-run with the same data, but add a POSITIVE, essentially 'undoing' what it did (while continuing to move forward only as a blockchain should.)
 +
 +- All penalties from **yesterday's run of the algo, can simply be 'undone'**. (Not exactly 'simply' on development side, but it is what will be accomplished.)
 +
 +- **Once the 'positive run' has taken place**, and everything is **back to the way it was pre-block-1575500**, the algo will then be **modified, all data points updated for the new network state and data from yesterday**, and **will be run again** - this time not penalizing accounts that were not actually self-sponsoring.
 +
 +- There was a LOT of effort put into the algo initially, to ensure it would not catch those who were not self-sponsoring. however, the network state is different now, and the algo needs some updates to the data points in order to fit better with the current scenario. This will be taking place after the initial 'positive penalty run'. 
 +
 +- Essentially all that happened is that the algo was a bit 'too sensitive' with a couple data points, due to the overall network state changes. That, plus the new data point being slightly incorrect, will both be resolved shortly.
 +
 +Those of you who have been around for a while probably realize that while there are sometimes issues with completely custom development within this community, and that things are always resolved. Those that are new, thank you for understanding the complexities. Apologies to everyone this issue affected. It will be resolved as soon as possible.
 +
 +===== January 20 2024 =====
 +
 +@here **Self-Sponsorship Algo** was run again (as was always planned). 
 +
 +however, we have come across a few concerns with the results. 
 +
 +Right now, the **data is being compiled and organized and will be shared with the community. **
 +
 +Once this has taken place, there will be an **opportunity given to those that were penalized unfairly.** (If they can prove it.)
 +
 +All data will be made public once it is made easier to read, and we will give details as far as how things will go from this point. 
 +
 +**If you believe your account was penalized without reason**, and **your algo score was under a certain number (TBD)**, you will be given a **chance to explain the data provided**. 
 +
 +**if your explanation adds up with the data**, and explains the **reason for the incorrectly applied penalty**, a blocksMintedAdjustment (credit) for the penalty blocks, and the blocks missed during the time incorrectly penalized, will be provided after the next update. 
 +
 +NOTE - This opportunity is **not a chance for everyone who was penalized to come and complain**. It is a chance to obtain a blocksMintedAdjustment and reversal of the blocksMintedPenalty for those **who were ACTUALLY penalized unfairly.**
 +
 +- **This will not apply to accounts with high algo scores. The algo's data is NOT incorrect, if your score was high you need not complain.** 
 +
 +- **The exact number for the chance to reverse will be decided once the data is compiled.**
 +
 +- This is only being offered due to an **additional data point that had one incorrect detail** and definitely caused at least one incorrect penalty we have noticed. It did not make a dramatic difference, so accounts with high scores need not concern themselves with trying to have them reversed.
 +
 +Another post will be made as soon as the data is ready to be shared. Thank you.
 +
 +
 +
 +**Discoveries thus far:**
 +
 +- There was only **ONE new data point added**, and that data point incorrectly pegged addresses that were both SENDER AND RECEIVER of transfer_asset transactions. It was only supposed to count SENDER. Any account penalized for this reason will **be taken care of.** 
 +
 +(The methods for resolving accounts incorrectly penalized are being considered, and details regarding how that will take place, will be published as discovered)
 +
 +- This was only supposed to be anohter multiplier added to the final score.
 +
 +- The 'tolerance' of the algo was set WAY too low... this will need to be adjusted.
 +
 +- Attached is a list of **address-with-scores.txt** - This is pulled from the algo logs and shows the scores applied to various accounts, and their registered names. sponsors with a score of >0 were included in the penalties, along with all of their sponsees. This is going to be modified, as there should be a 'minimum threshold' for that to take place.
 +
 +- Further details compiled from the algo's log will be published as it is created, we are writing scripts to consolidate it and make it easier to read.
 +
 +- The algo will be getting some tweaks, as they are obviously needed. 
 +
 +- DO NOT WORRY - the accounts that were penalized without reason WILL be restored. The restoration just has to be done very carefully as to not cause further issues. We are going over the code now and have found multiple changes already that can and will be made. 
 +
 +- Once the modifications to the algo take place, and its tolerance is adjusted, it will continue to be active, and have continual modifications over time to dial it in further. 
 +
 +- The details in regard to the 'reversing' of penalties will be published as well. Those details are still being worked out. 
 +
 +Apologies for the inconveniece caused.
 +
 +{{ :address-with-scores.pdf |}}
  
 ===== January 17 2024 ===== ===== January 17 2024 =====
Line 751: Line 882:
 - Updated Japanese translations (Credit: R M) - Updated Japanese translations (Credit: R M)
  
-Committed by @CalDescent1:+Committed by Cal:
  
 - Added developer QDN proxy. - Added developer QDN proxy.
Line 1776: Line 1907:
 ===== February 24 2023 ===== ===== February 24 2023 =====
  
-@here This is some **VERY IMPORTANT INFORMATION for Qortal Users to READ** - from our **amazing lead core developer, CalDescent.** - I think understanding the nature of the platform, and how much goes into its development is a really good idea for people to at least partially understand.+@here This is some **VERY IMPORTANT INFORMATION for Qortal Users to READ** - from our **amazing lead core developer, Cal.** - I think understanding the nature of the platform, and how much goes into its development is a really good idea for people to at least partially understand.
  
 Reading this information I think should give at least a very small idea of just how difficult and tedious developing a platform like Qortal really is...  Reading this information I think should give at least a very small idea of just how difficult and tedious developing a platform like Qortal really is... 
Line 1789: Line 1920:
 -crowetic -crowetic
  
-from CalDescent:+from Cal:
 There are two parts to a blockchain system - the blocks themselves, and the derived state from these blocks (often referred to as the "chainstate"). Every time a new block is added to a node's local chain, it updates its chainstate based on the information in those blocks. These state updates come from transactions, AT executions, and reward payouts. However, there are multiple candidates for each block (currently all level 5 and above will mint their own version of every block), so the node will have to re-org to different versions of the block for that height until it is confident that it has the best block available from all the candidates on the network. There are two parts to a blockchain system - the blocks themselves, and the derived state from these blocks (often referred to as the "chainstate"). Every time a new block is added to a node's local chain, it updates its chainstate based on the information in those blocks. These state updates come from transactions, AT executions, and reward payouts. However, there are multiple candidates for each block (currently all level 5 and above will mint their own version of every block), so the node will have to re-org to different versions of the block for that height until it is confident that it has the best block available from all the candidates on the network.
  
qortal_status_updates.1705532135.txt.gz · Last modified: 01/17/2024 17:55 by magic_ink

Page Tools