This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
qortal_status_updates [01/20/2024 19:28] – magic_ink | qortal_status_updates [01/30/2024 20:02] – magic_ink | ||
---|---|---|---|
Line 5: | Line 5: | ||
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 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). | ||
- | **CURRENT CORE VERSION:** 4.4.2 | + | **CURRENT CORE VERSION:** 4.5.0 (Jan 30th 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 18: | Line 18: | ||
**CURRENT TRADE FEE:** 0.011 QORT | **CURRENT TRADE FEE:** 0.011 QORT | ||
+ | |||
+ | ===== January 30th 2024 ===== | ||
+ | |||
+ | |||
+ | |||
+ | **CORE version 4.5.0 has been pushed with Algo resolution. ** | ||
+ | < | ||
+ | |||
+ | 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:// | ||
+ | |||
+ | for Mac, use this for now: | ||
+ | https:// | ||
+ | |||
+ | ===== 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**. | ||
+ | |||
+ | 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 ' | ||
+ | |||
+ | - It was discovered that the algo can essentially be set to ' | ||
+ | |||
+ | - All penalties from **yesterday' | ||
+ | |||
+ | - **Once the ' | ||
+ | |||
+ | - 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 ' | ||
+ | |||
+ | - Essentially all that happened is that the algo was a bit 'too sensitive' | ||
+ | |||
+ | 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 ===== | ===== January 20 2024 ===== | ||
Line 70: | Line 138: | ||
Apologies for the inconveniece caused. | Apologies for the inconveniece caused. | ||
+ | |||
+ | {{ : | ||
===== January 17 2024 ===== | ===== January 17 2024 ===== |