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 revisionBoth sides next revision
qortal_status_updates [01/20/2024 19:31] – magic_inkqortal_status_updates [01/21/2024 17:24] – magic_ink
Line 18: Line 18:
  
 **CURRENT TRADE FEE:** 0.011 QORT **CURRENT TRADE FEE:** 0.011 QORT
 +
 +===== 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 ===== ===== January 20 2024 =====
qortal_status_updates.txt · Last modified: 03/03/2024 13:13 by cal

Page Tools