It's so easy to call all disappointed users "fudders", but it's a fact - zPIV locked without any notice by public channels. I hope your understand difference (for end-users) between closed chats like discord and public services like twitter, forums, official website, etc.
You know, I'm with PIVX since 2016 and all mandatory updates comes with fails: migrating from PoW to PoS, when blockchain was rolled back several times a week; adding zerocoin, with automint enabled by default, and people start losing their funds (yes, it was restored after some updates, but time and nerves was wasted).
It's all don't matter when coin don't have any real world uses and looks like this case still actual for PIVX - spork was activated March 7th and only 2 users (me and one on reddit) noticed it. Can you imagine what will happen if BTC or ETH will locked for several days?
PS: "Fast, secure, anonymous" they said, "Be your own bank" they said - oops, "zPIV disabled due to maintenance".
PPS: For some reason mentioned DASH (lol, it's stupid excuse of own fail by point to another coin) don't have any sporks, which make all your funds impossible to use.
this is actually fair response, most have been concentrated (as far as communication) in discord there is an important-update section and it was announced there, due to massive cloning of this coin this update onto itself might not be trivial (cause team needs to message out details to others that might be in a type of alliance with it)
also a recent change was made for pending 3.2 update to inject message onto QT wallet itself (going forward) see. :
https://github.com/PIVX-Project/PIVX/pull/832and as you know place is quite competitive so the update is kept low key as far its details
we could definitely do better job at communication and many parties do and spend great deal of energy but that is not happening so much on this forum, and twitter is also (to me at least) not the best place to broadcast sensitive update announcements .. hence discord.. probably best place for now where this was done
thanks for clarifying your post though, nice response
