Proposal “mobile-privacy“ (Closed)Back

Title:Decision Proposal: Support for Dash's User-Facing Features (Privacy and Usernames) in Both Mobile and Desktop Wallets
Owner:decision_proposal
One-time payment: 1 DASH (51 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2023-07-12 / 2023-08-11 (added on 2023-07-15)
Final voting deadline: in na
Votes: 172 Yes / 127 No / 90 Abstain

Proposal description

UPDATE: The intent of this proposal is in line with Option C of QuantumExplorer's comment below.

This is a decision proposal to decide whether Dash’s official products intended for end users, namely the mobile and full-node desktop wallets, should support all of Dash’s end user features, namely CoinJoin and usernames/contact lists (when released). Initial signatories supporting this proposal include PAX, Hilawe, Kanuuker, Dandy, Rion, Yaphsad, Flip, Mastermined, Arthyron, z37da, vampyren, and dashfriend.

At present, the official Dash mobile wallet does not support CoinJoin mixing or sending private transactions. This is an explicit decision by Dash Core Group to not include these features in the mobile wallets, and at the moment there is no plan to add them.

Additionally, the Dash Core full-node desktop wallet is not initially slated to support Evolution usernames and contact lists.

We believe that Dash’s status as the best digital cash in the world is the result of all its features intended to facilitate this purpose: security, speed, low fees, privacy, and soon, human-readable usernames and contact lists. We believe that the Dash experience should be available to all Dash users, and to this end, at a minimum, the official end user wallets should be able to faithfully deliver this experience.

Please vote YES if you want Dash’s user-facing features (privacy and usernames) to be supported by DCG’s end user-facing products (Dash Core desktop and mobile wallets).

Please vote NO if you want DCG to continue to choose which of its end user projects support which end user features.

Please vote ABSTAIN if you are indifferent to the outcome.

If this proposal passes by the usual proposal rules (a net 10% of active masternodes voting yes), it will be considered as this decision proposal passing and the YES outcome taking effect.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
2 points,3 years ago
I'd like to know why the hell there are MNOs that are voting "No" on user-facing privacy features. WTF! That has and should still be one of the pillars of xcoing/darkcoin/DASH. Why the hell would someone be a MNO and vote down one of the most important concepts that defined DASH since the beginning. brutal. Definitely a yes vote from me.
Reply
0 points,3 years ago
Because coinjoin on mobile would be a shit experience.

I want to see the best privacy and privacy experience on dash mobile and coinjoin is dated AF.
Reply
-1 point,3 years ago
Many MNOs are voting "NO" because Dash is infiltrated by government agents.

The dash community is doomed unless you decide to invest in mnowatch and dashwatch, record all the votes and punish the bad actors.
Reply
4 points,3 years ago
My guess is people didn’t like the way the proposal was formulated, for one reason or another. I think we all value privacy here.
Reply
2 points,3 years ago
You may value privacy, but the government agent that want dash to be destroyed, they dont.

And we have a lot of them here.
Reply
2 points,3 years ago
And by the way, here you are the 130 masternodes who voted against this proposal

https://mnowatch.org/the_results_dashd_2023-07-24-08-12-33.uniqueHashVotes.168.html?4=MOBILE-PRIVACY
Reply
3 points,3 years ago
The conclusion is that most of the agents are hiding now in crowdnodes.

Thats why a crowdnodewatch is urgently needed.
Reply
3 points,3 years ago
Interesting observation. It would make sense for bad actors to target crowdnode, because they have supercharged voting there. Better governance bang for the buck.
Reply
3 points,3 years ago
And by the way, there is no bigger proof that the crowdnode is FULL of government's agents, than the recent vote results. Have a look.
https://cdn.discordapp.com/attachments/505116948359675924/1132640361664221214/image.png

NOT A SINGLE YES_VOTE FOR THE ENCOINTER PROPOSAL BY CROWDNODE.

Tottaly reverse of what everybody expected. Everybody assumes that the crowd should be a proponent of the encointer project , as long as the crowd will get a basic income when encointer is established.

Why the crowd didnt cast a single yes vote? Simply because crowdnode is full of agents who vote against the benefits of dash.
Reply
2 points,3 years ago
Good governance without a Proof of Personhood cannot happen.

The dash community is doomed unless they decide to join the pioner Encointer community or any other proof of persnonhood community that will appear in future.
Reply
2 points,3 years ago
Any proposal that seeks to improve Dash's privacy, or improve access to it, or even re-brand it is going to get my support. Financial privacy and digital cash go hand in hand.
Reply
2 points,3 years ago
Sorry to see so many Nos on this proposal, Dash is falling behind competitors on Mobile.
Reply
4 points,3 years ago
UPDATE: The intent of this proposal is in line with Option C of QuantumExplorer's comment below.
Reply
2 points,3 years ago
The impetus behind this proposal was hearing first-hand that DCG did not intend to implement privacy functionality in the official mobile wallets. Not that it wasn't the highest current priority, but that it simply would not be implemented.

I joined Dash because of privacy initially, and it's been incredibly frustrating working to onboard new services and communities, such as Spritz and Maya, and seeing all the questions roll in on how to use Dash's flagship privacy feature. Meanwhile, every meaningful competitor is ahead of Dash in this regard. An up-and-coming multi-coin wallet is even adding privacy functionality for Bitcoin, Bitcoin Cash and Litecoin, making all these able to be used more privately than Dash. It's becoming increasingly difficult to make a strong case for using Dash over these.

Non-DCG avenues haven't worked out either. Electrum mobile, while always buggy, technically worked, but no longer does since maintained by the Incubator. Many privacy wallet concepts have come through the Incubator over the years, none of them going anywhere. I feel like each passing year we're losing our digital cash title. I can't in good conscience continue to advocate for a form of digital cash that doesn't offer even basic privacy protections when other options are available.
Reply
3 points,3 years ago
I'm inclined to vote yes under Option C that Quantum floated
Reply
5 points,3 years ago
I want to start off by saying that I am not against this proposal and that I'm quite happy about engagement like this.

I would however like a little more clarity.

Would a YES outcome mean:
A) that these features should be added to our roadmap to be done at a time that makes sense.
B) that DCG should do these immediately and drop what we are currently working on that don't go in this direction.
C) that DCG should prioritize these items after we have completed what we are currently working on.
D) Something else.

Some things to consider:

I estimate that getting Dash Core to support usernames would take about 2 people between 4 to 8 months depending on the developers put on the problem. This is something I would personally support and even though it's not on the roadmap, we would have gotten around to this when we had the manpower to do so.

Currently we also have doubts that our current Coinjoin system would work on iOS. To be clear I am not saying it won't, we just are not yet sure until more investigation has been done by our developers (that have been focused recently on other parts of the project).
Reply
3 points,3 years ago
Option C is the original intent of this proposal.
Reply
2 points,3 years ago
I am only speaking for myself, not the other signatories.
I would clarify it as being option C. Get Evo out the door then focus on flushing out the ecosystem fully.
Reply
2 points,3 years ago
Agreed. I discussed this ambiguity with the author before it was submitted. Hoping to see it clarified.
Reply
2 points,3 years ago
Author should have paid more attention to you then, as now multiple people have raised it as an issue.
Reply
1 point,3 years ago
I agree, this needs to be more specific. However to help the PO update this and for the network to make an informed decision, can you tell us:
- What is DCG currently working on for the mobile wallets?
- From previous testing it looks like DashPay on mobile is largely complete, is this accurate?
Thank you.
Reply
0 points,3 years ago
Would you mind explaining to all of us MNO, whether v20.0 will have convertibility of Platform Credits back to Dash somehow restricted, and if that's the case, will the Platform Credits be somehow trapped in Evo?
The MNO deserve better than the silence from the few in the know.
Don't you feel the MNO who in good faith decide to convert their 1K Masternodes to 4K HPMN have a right to know what exactly comes with v20.0?
Reply
3 points,3 years ago
You can freely convert from Dash to Credits, and Credits to Dash, no barriers. I didn't know I was holding back any information on this.
Reply
0 points,3 years ago
Thank you for sharing this.
Reply
3 points,3 years ago
YES for CoinJoin / PrivacySend and Blockchain-registered usernames to be supported by Dash Core desktop and mobile wallets.

With the notion that these features should be added to the Dash Roadmap to be done at a time that makes sense (which to me should be after the launch of Dash Platform on Dash Mainnet, to avoid further delays).
Reply
2 points,3 years ago
To be clear this means YES to extending CoinJoin / PrivacySend to Dash Core mobile wallets and extending Blockchain-registered usernames and contactlists to Dash Core desktop wallets.
Reply
1 point,3 years ago
Changed my votes to NO, after learning that the proposal owner considers a YES vote in line with QE option C, while i consider my YES vote in line with QE option A. Makes it difficult now to vote YES on this for me.
Reply
1 point,3 years ago
Why do people put up proposals telling DCG to do a job other than what they are focused on. You want this done so badly, propose to do it, do it and get paid. In the mean time, DCG needs to focus on Evo, then focus on all the final touches of evo. I suspect evo will make implementing mixing on mobile much easier, and I'm also sure that they'd do it regardless of a vote, when they have the time.

I won't vote yes on these proposals simply because I don't agree with superseding the existing road map. Sure, I want to mix from my mobile wallet, but it's not as important as delivering evo.

What does saying yes even mean? I wish these waste of time proposals would stop, we can't afford to do these nice projects right now anyways.
Reply
1 point,3 years ago
'What does saying yes even mean? I wish these waste of time proposals would stop, we can't afford to do these nice projects right now anyways.'

It is the side effect of having both a low Dash price and low Dash proposal fee. I expect a lot more of these proposals hitting the Dash network to be honest.
Reply
2 points,3 years ago
With 'these proposals' i mean hastely made, inprecise, low quality, decision proposals.

I just wish people proposing decision proposals would stop asking any Dash for it.
They should just use the default proposal generator and ask for 0 dash.

At least this one does not have a multi time period (10 months / 12 months) attached to it and has a somewhat interesting topic for discussion.
Reply
1 point,3 years ago
Inclined to vote yes, as long as it doesn't degrade mobile wallet performance, like putting a cap on mixing rounds and offering 2 rounds of mixing for Mobile.
Reply
-2 points,3 years ago
A better idea would be for DCG to float separate Supplementals for allocated and unallocated funds and let the voters decide.
Reply