There was a video demonstration about passing PIVs to ZPIVs manually, although the disproportionate automint made it not necessary to do so, as many people found themselves with excess ZPIVs. Have you thought of doing a reverse, ZPIVs to PIVs, to unify criteria in that process that affects so many people? It could save a lot of particular actions that are made due to ignorance or technical limitations of the users that you later look forward to correct. The devs team should always keep in mind that PIVX maintainers are not programmers.
An auto-reversal of minted zPIV back to PIV isn't desirable whatsoever as it will need to be sent back to "some" address.
Some people may also prefer having most of their balance as zPIV due to its anonymity. It's better done manually IMO.
Do you still prefer the automint activated by default? I understand that the ACTIVE action coming from a unilateral/centralized decision that totally falls within the personal scope of the holders and in their right to own Zpivs or not, is that of the automint, and that this action should be no longer limited, but "not enabled" by default, but ok, it's good to report that it may be limited and how, thanks.
Although I'm on the fence on that question, I believe that auto-mint is required to achieve the goal of increased zPIV liquidity.
Goal from day 1 of PIVX was to integrate a full time anonymous crypto currency. This is an attempt to get closer to that goal.
Keep in mind, this is only zPIV version 1.0. As we improve zPIV integration further, we may be able to achieve full-time zPIV.
The expectations of an active and functioning zerocoin are splendid, there we all agree and the massive collaboration of the community in terms of their unconditional disposition to the guidelines of the programming team is the greatest proof of it ... but it would not be better dump before their analysis 100% and their work in rebalancing the balances of the huge amount of wallets affected ... to continue after advancing in the zerocoin all together? The synchrony of the project is very important.
As mentioned above, the goal of PIVX is to achieve the most private crypto currency that is also fully transparent when required.
Although the bug causing excess zPIV minting was unfortunate, it showed how much PIVX could handle. (over 1000 tx / block!)
Very good post.Splendid and veyr necessary explanations.
I greatly appreciate your contribution to the rebalancing of the situation, jakiman. Huge and very honestly. I am also aware that establishing a clear and effective channel of action before so many people and their varied capacity for understanding and response is very delicate. But ... beyond that, which is reflected very positively in your post, could you make an extra effort in the follow-up that this information has on the players and their operations? I mean answering your later questions - or delegating to someone who does, but identifying yourself as a member of the devs team , so as not to lose the unity of criteria that can be given by contributions, well-integrated, but outside the official group - so they have the right concepts before taking any steps that can affect both your balance sheets and the stability of the system. That is hugely important for everyone - and I am allowed to re-focus on the technical limitations of the various users of PIVX.
Finally, my main question, as a basic user of PIVX, would be the following: Wait for the final wallet creates added risks? Do you see it inappropriate or dangerous for technically limited users?
Thank you very much, greetings and good, the best luck for our boat.
Thank you.
Please note that I am not a developer. I am just like anyone here but who has just been VERY active & dedicated to assist PIVX's success for a very long time.
As for your main question, we are currently asking for everyone to install and run 3.0.4 RC3 right now. No other versions.
If my guide isn't easy enough to follow, then I hope they ask for assistance though many channels that we have available.
But if afraid, they can wait for the final stable release which we hope will happen later this week pending RC3 results.
Poll
