To-Do for Pump Group Releasescan for previous registrations to know which stealth transactions will relay the pick for the current pumpscan for said stealth transaction and extract the pick informationscan transactions belonging to the registration address to report the minimum balancegui refinements (lock input fields for manual entry and other "fool-proofing")full-cycle testing and associated debugging- block reward adjustment (assuming consensus for higher rewards remains unchallenged)
- deployment (
versioning, building, & bundling)
Before I get to the update, I would like to mention that, in addition to bumping block rewards, I want to increase the block time, most likely to 4-6 minutes. Block times are currently 2 minutes. I dislike how fast the chain is growing right now. Short block times gained in popularity when it was assumed that quick confirmations might lead to vendor adoption. However, new technology has become available that obviates short block times. Probably the best example is Vanilla Coin's zero time.
Now to the update.
I finished the GUI "fool-proofing", added the new version information, and have done many full-cycle tests successfully. I only need to put in the new block rewards and then build. I should have a beta release (version 1.2.0.0, protocol 62200) within 24 hours. During the beta testing period, I will streamline the code so that updating the GUI less CPU intensive than it is now. Mostly, I will set up some caching. For example, I presently execute a full search for the pick transaction on every new block. I wrote this code to be very efficient already, but the best behavior is to not make a search if the results are already available.
Users may not notice the improved efficiency because the present behavior is very fast. However, I consider it good practice to reduce the work load on the CPU, if possible.
I also need to provide feedback if a user has already registered for a pump, but I feel like that can wait for the beta testing period. Presently, users will be required to remember if they have already registered. In the future, the registration status will be indicated in the pump page.
I would have loved to have pushed changes to the github repository tonight, but I decided that I should change the block rewards before pushing. I'm certain that in the remote chance that I don't have builds tomorrow, I will be at a stage where I can push the source code changes to the repository.