Code:
Name: LMP - Quality Ctrl
Term: 1 Cycle
Cycle Amnt: 3,000
Total Amnt: 3,000
Author: JSKitty, Mirela
Receiver: PIVX Labs
Address: DLabsktzGMnsK5K9uRTMCF6NoYNY6ET4Bb
Created: 03-03-2024
Status: Active
Vote Hash: 287773364ed0407337c84686b5467f9e8d1c60272cc47436fe82511646e08e60Note: The original intended name was LMP - Quality Control, we submitted it as LMP - Quality Ctrl to ensure the title and URL fit consensus requirements.
Note: Thanks to the price increase of PIV, PIVCards and PIVX Rewards QC is now cheaper, and reward priorities can be slightly dropped to account for the price increase, as such, this proposal drops from 4,000 PIV to 3,000 PIV.
Proposal Abstract
This proposal is a renewal proposal to cover the full costs of the Labs Quality Control process, this is a continuation of the previous proposal, here.
This process was originally devised as of September's edition of The Superblock Report, which outlined that the vast growth of My PIVX Wallet's user-base calls for a much tougher review process, both for Code (Developers) and App Quality, the latter of which is handled by the newly formed Quality Control team.
This was accelerated when various data-loss and fund-loss bugs were detected after the v1.0.0 release (Bug #1, Bug #2), concerning Proposal Submission, where we discovered and replicated multiple bugs that could cause a loss of either the proposals submission fee, or worse, the entire 'wallet' database would be lost - if such a bug hit a user that did not backup their seed phrase (as we recommend), they would have permanently lost their funds without possibility of recovery.
These bugs, although critical; were very easy to find even by non-developers, and thus we launch the Quality Control team, after now over a full month of successful trialing, which has shown to reveal far more bugs in-advance (particularly @MiguelC030 who has participated in almost every test I can remember) and this allows us to refine new additions further before merging, ensuring each new feature or improvement is fully acceptable from a user's perspective.
How'd the last one go?
The last three months of Quality Control expenses (4,000 PIV) were primarily spent on MyPIVXWallet Shield, MPW v1.5.0 refactors, and the new PIVX Rewards platform.
The last three months required heavy testing for the release of MyPIVXWallet v1.5.0, containing the long-awaited SHIELD feature, additionally MyPIVXWallet had quite a lot of refactoring updates and GUI ports due to the Vue transition, each of these required testing, especially Shield, which received the heaviest amount of testing and QC funding.
For the PIVX Rewards platform: a 100-user testing process started in February, all 100 initial users received a reward boost for using the platform and sharing their feedback, and within just a single week of feedback, we got the platform to a state that users almost unanimously enjoy using it - this platform releases in early March, watch out!
How are Quality Control rewards determined?
Each Pull Request is assigned a "complexity" or "size" marker by a Labs Team member, this is assigned based on the developer's interpretation of the complexity (or operational importance) of the Pull Request.
The current Labs Quality Control distribution table is:
| Size or Complexity | Reward Amount | Description |
|---|---|---|
| Trivial | 10 PIV | Trivial app adjustments, such as small improvements or bug fixes. |
| Small | 20 PIV | Noticeable changes or UX-affecting refactors, such as Design or Functionality. |
| Large | 50 PIV | Major app changes, such as large new features, large refactors or patches. |
| Critical | 100 PIV | Critical and time-sensitive changes, such as patching data-loss or fund-loss bugs, large protocol changes such as Shield or Deterministic Masternodes. |
In the case of other services, such as PIVCards where testing requires actual purchases, users are given a select amount of PIV between 20-100 and allowed to spend the PIV on various PIVCards items, this allows us to watch the backend during real-time tests and iron out any issues that are spotted ahead of launch, or ahead of new updates, the most important aspect of this is having MANY users participate, from different regions, which grants us a bigger testing surface area over more brands, countries, currencies and languages.
For PIVX Rewards, the platform rewards users autonomously based on the price of PIVX - the higher the price, the lower the PIV reward to hit equalibrium, all Quality Control members receive an additional 100% reward boost for their active work in the design and development process of the platform.
Last edited: